LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

RT Build and Deploy cRIO - Why Extra VI Compile

Hi all,

 

We are developing a somewhat extensive embedded application that runs on a cRIO-9049

The project is constructed with

- multiple libraries (not packed )

- no shared variables

- no load from references

- many vis are inlined for performance

- VI have 'separate compile code' option

- the project as about 2000 VI

 

When I build the application with many of the compiler options but not

- remove type_def 

- not remove inline VI diagram

 At the end of the compiler process it saves all the VI... I guess with the optimized compile code.

 

The big mystery is when I come to ' Set as startup', there is an additional compilation of up to 100 VIs ad then the deployment loads in another large handful of VIs.

My questions are:

1. if I have just build an exe why is there more compilation at deployment

2. Why is there extra deployment of VI.  I would have thought that there ALL contained in the startuprt.exe 

3. If we have an extensive library structure in the BUILD config do I need to link the libraries in using the 'Always Include' options

 

thanks in advance

 

 

Message 1 of 1
(1,724 Views)