LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Is there any reason to use the "Small target file with external file for subVIs" option in App builder?

When building a LabVIEW executable, is there any advantage or disadvantage to using the option:

"Small target file with external file for subVis"

We've been using this option, but it causes issues with the Report Generation Toolkit since the Application directory is that of the executable and not that of the library file where the dynamic VIs actually are. So now we're questioning whether there is any advantage to using the option at all. The only reason I could think of is that it would give you the ability to swap out individual vis in an executable version. This might be useful for a test executable. Are there any memory or speed advantages?
0 Kudos
Message 1 of 3
(2,534 Views)
You nailed it on the head with the advantage. This option allows you to easily modify your application by changing the subVIs. Since they are not part of the executable, you do not have to build a new executable every time you change a subVI.

As far as memory, this option saves memory becuase your application is not as large. When it is loaded into memory, the dynamic VIs are not automatically loaded. They are only loaded when you call them. Therefore, it uses less memory.

However, on the same token, since they are not loaded with the rest of your application, this must be done at run-time which can slow down the execution of your application. They have to loaded the VIs, execute them, and then unload them which consumes more execution time. Which choice
is better just depends on your memory and speed needs.
J.R. Allen
0 Kudos
Message 2 of 3
(2,534 Views)
I do not have the information to specifically answer your memory/speed question. I recommend experimenting. Here is what I found in the LV online help.

Small target file with external files for subVIs�Embeds the top-level or exported VIs and any dynamic VIs in the executable or shared library. The subVIs for the top-level and dynamic VIs are stored in a single VI library. The resulting file is smaller than a single file that contains all VIs.
0 Kudos
Message 3 of 3
(2,534 Views)