Hi there! An interesting feature of LV 2011 is the possibility to separate (detach) the compiled code from a VI, which is mostly useful for source or version control purposes (if you modify a VI that is called by a bunch of others, only that VI will appear as "modified", whereas in the past, all calling VIs would be recompiled and appear "modified", although there actual diagrams and panels would remain identical). One of the warnings in the help file, though, is that since the compiled code is cached in some other location than the VI, you are discouraged from using that if "you intend to load or run using the LabVIEW Run Time Engine". I am not sure I am quite clear how this works for a project that I will eventually want to release as a standalone application. Does it say that I cannot detach the compiled code from any of the VIs in the project? Of any dynamically called VI in the project? Or it does not apply (if everything is recompiled for the standalone application)? Thanks for clarifying.

Yes, a source distribution. Alternatively, you could try using something like VIPM to build your collection of VIs. Never having created an application which needs this, I can't offer any practical advice (assuming you even need it).

ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW

separating compiled code question

Solved!

Author

Found somewhere else on the forum a link to this tool which I used and seems to be doing the job just fine.

Message 11 of 11

(497 Views)

LabVIEW

separating compiled code question

Re: separating compiled code question