Repository navigation
Docker Image
- nationalinstruments/labview:2026q1-<linux/windows>
- Docker Hub: labview:2026q3
- Base Images:
- Windows: Windows Server 2022 LTSC
- Linux: ubuntu 22.04 LTS
- LabVIEW Version: 2026 Q3
- Images:
- Windows: labview:2026q3-windows
- Linux: labview:2026q3-linux
What's New
- New argument
-BuildDirectoryadded to LabVIEWCLIExecuteBuildSpecoperation. To run this operation in the CLI for LabVIEW, execute a command with the following syntax:
LabVIEWCLI -OperationName ExecuteBuildSpec -ProjectPath <path to project> -TargetName <name of target> -BuildSpecName <name of build specification> -BuildDirectory <path to output directory>- Used to specify the absolute path where the final build artifact (like a DLL or EXE) should be saved.
Consider the following when using the -BuildDirectory argument:
- Using the
-BuildDirectoryargument doesn't permanently modify your build specification when changing the build destination for your application or library. - You must specify both
-TargetNameand-BuildSpecNameto use-BuildDirectory. If either argument is missing, the LabVIEW CLI returns an error. - The
-BuildDirectoryargument only overrides the Destination Directory and Support Directory paths. Using-BuildDirectorydoesn't affect custom directories defined in the build specification These directories remain at their originally configured locations. - The
-BuildDirectoryargument applies to Application (EXE), DLL, Source Distribution, .NET Framework Assembly, Packed Project Library, ZIP, Installer, and Package (NIPKG/IPK) build specifications. - The
-BuildDirectoryargument doesn't support FPGA build specifications.
Refer full documentation here: Predefined Command Line Operations