Why does my compiled exe ask for the location of subvis when installed on another computer?

[Corny · Accepted solution]

static 🙂

but here is a solution you can use:

When you build your exe use the following settings as shown in the attachments.

[Matthew_Kelton]

If you have static VI calls, which is sounds like you do, nothing shoulw be in the Always Include section.  LabVIEW by default includes all subVIs that are statically called by any VIs in your Startup VIs section.

The default method is for LabVIEW to build all the VIs into the EXE.  Corny's suggestion will create them locally in a subdirectory.  Unless you really need this behavior, I see no reason to do it.

[Corny]

this creates a folder called SUbvis outside your exe and puts all the subVI's from the folder I called "subvis" in there, and the exe will use the correct paths linked to that folder.

You must ofcourse create an own "destination" folder to these subvis first, and let them be installed to that folder.

When building the installer, the paths should automatically look the same and it should include these VI's (dont think you need to include any subvis in there tbh 🙂

[Corny]

Matthew,

yes your totally correct - but you can update functions outside of the exe, (but need to compile these functions first - wont work otherwise as of I know). Ive an application whit an pluginstructure where I use this, but there instead of using compiled VI's the plugin is compiled as an LLB that holds the plugin functions - for easy adding additional functionality to an already running exe. Otherwise there is really ...no point... as you say 

[Sam_Sharp]

Thanks for all your help - that worked, it no longer struggles to find the SubVIs on launch (I had the project subdirectories containing the SubVIs in the 'always include' section).

Thanks.