LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Programmically mass compile under LV runtime

I'm attempting to distribute source code to a customer in an installation package and finding it useful (if not neccessary) to perform a mass compile on the software. To keep things simple for the customer, I want to have a program (VI) run after install that will perform the mass compile.

The mass compile that comes with LV will work under the run time, however does not seem to run independantly (even using VI server to push buttons).

I have managed to do something like a mass compile by using brute-force methodology: loading every VI from a base path and then saving each one before unloading any of them.

Does anyone have ideas on how to improve this?
0 Kudos
Message 1 of 4
(3,477 Views)
You can see the same question here. Make a VI that has an Open Application Reference and an Invoke Node. Select as the method Mass Compile and pass it the directory or llb you want to compile. Have the in
staller include this VI and run it after installation.
0 Kudos
Message 2 of 4
(3,477 Views)
Actually, the solution referenced does not resolve the problem as I am attempting to do this under LabVIEW runtime. The Mass Compile invoke node is only available with the full version of LabVIEW, not the runtime engine.
0 Kudos
Message 3 of 4
(3,477 Views)
LabVIEW Run-Time cannot compile VIs. Its purpose is for execution only. To mass compile, LabVIEW Development must be installed on the target machine. However, a VI running in Run-Time can invoke the "Mass Compile" method of LabVIEW Development opening an application reference to it, as it was suggested previously.


LabVIEW, C'est LabVIEW

0 Kudos
Message 4 of 4
(3,477 Views)