Application Builder: Difference between revisions

Latest revision as of 00:58, 19 March 2024

The Application Builder (AB) provides tools for creating and deploying stand-alone applications developed in LabVIEW. Its purpose is to provide the functionality to build, or compile, code into standalone executables and/or installers. It also can compile or package code in other ways. The following types of Build Specification exist:

Depending on the LabVIEW version you have one or more of the above options might be missing.

Build Specification Dialog

Build Specifications are created by right-clicking Build Specificaitons in the Project Explorer window, then selecting New, and one of the Build Specificaiton Types listed above. The Build Specification dialog will launch for the selected type and show all the options available for building that type of item.

See Build Specification dialog.

Application Builder API

An API for the Application Builder is available and can be found in the Application Builder Palette.

Symbolic paths

Inside the Application Builder, LabVIEW uses several symbolic paths to have environment-dependent variables.

Symbolic path	Contents	Usage
NI_AB_PROJECTNAME	Name of the project	Automatically place the build in a folder that is named after the project
NI_AB_TARGETNAME	Name of the (Real-Time) target

@@ Line 1: / Line 1: @@
-{{TOCnestright}}<br>
+{{TOCnestright}}
-= Introduction<br>  =
+The '''Application Builder (AB)''' provides tools for creating and deploying stand-alone applications developed in LabVIEW. Its purpose is to provide the functionality to build, or compile, code into standalone executables and/or installers. It also can compile or package code in other ways. The following types of Build Specification exist:
-The application builder (AB) is a part of the LabVIEW Project environment, it has the possibilities to distribute your code in various ways:<br>
+* [[Build Specification/Application (EXE)|Application (EXE)]]
+* [[Build Specification/Installer|Installer]]
+* [[Build Specification/.NET Ineterop Assembly|.NET Ineterop Assembly]]
+* [[Build Specification/Package|Package]]
+* [[Build Specification/Packed Library|Packed Library]]
+* [[Build Specification/Shared Library (DLL)|Shared Library (DLL)]]
+* [[Build Specification/Source Distribution|Source Distribution]]
+* [[Build Specification/Zip File|Zip File]]
-*Executables<br>
+Depending on the LabVIEW version you have one or more of the above options might be missing.
-*DLLs<br>
-*Source distributions<br>
-*Web services<br>
-*Installers<br>
-Depending on the LabVIEW version you have one or more of the above options might be missing.<br>
+== Build Specification Dialog ==
+Build Specifications are created by right-clicking '''Build Specificaitons''' in the [[Project Explorer]] window, then selecting '''New''', and one of the Build Specificaiton Types listed above.  The [[Build Specification dialog]] will launch for the selected type and show all the options available for building that type of item.
-<br>
+See [[Build Specification dialog]].
-= Manual<br>  =
+== Application Builder API ==
+An API for the Application Builder is available and can be found in the [[Functions Palette/Programming/Application Control/Application Builder|Application Builder Palette]].
-{{Stub}}<br>
+== Symbolic paths ==
-= Advanced<br>  =
+Inside the '''Application Builder''', LabVIEW uses several symbolic paths to have environment-dependent variables.
-The application builder has several interesting advanced uses<br>
+{| class="wikitable"
-== Automatic building<br> ==
-You can use a VI inside vi.lib that can build without user interaction. The VI is located in <span style="font-style: italic;">&lt;</span>''vi.lib&gt;\AppBuilder\BuildTargetBuildSpecification.vi''. This VI takes a project path and optionally a build and target name as parameters.<br>
-== Symbolic paths<br>  ==
-Inside the application builder LabVIEW uses several symbolic paths to have envorinment dependent variables.<br>
-{| cellspacing="1" cellpadding="1" border="1" style="width: 708px; height: 104px;"
 |-
 ! scope="col" | Symbolic path<br>
@@ Line 39: / Line 34: @@
 | NI_AB_PROJECTNAME<br>
 | Name of the project<br>
-| Automatically place the build in a folder that is named after the project<br>
+| Automatically place the build in a folder that is named after the project
 |-
 | NI_AB_TARGETNAME<br>
@@ Line 45: / Line 40: @@
 | <br>
 |}
-<br>
-<br>
-<br>
 [[Category:Building executables]]