Table of Contents
15 Executable
Location
For built exe locations, see Deployment Structure: Execution
Build Spec
The EXE build spec of the template application project uses the following settings in order to build an executable:
Make sure to add the /Modules folder to the “Always included” section, so that any dynamically loaded (and thus not statically linked) VIs are added to the binary artefact.
DLLs and Shared Libraries
For guidance on how to include Shared Libraries (DLLs, .so, .py etc), see the following pages:
-
Configuration for Executables
The HSE Application Template can be configured to use non-default locations for the config and the data folders. See Configuration - Alternative Paths for details.
LabVIEW allows specifying a customized .ini configuration file when building an executable. This .ini file will have the same name as the .exe file and will be copied into the same folder as the .exe. See the NI's knowledge base article on combining an .ini with an executable.
CLI Arguments
You can call the executable with CLI arguments, e.g.
C:\>TEMPLATE.exe -- "one cli param" "another cli param"
To receive them in a module, use the
Get CLI Argumentsrequest of the UI-Manager.