Application Builder: Difference between revisions
m removed unnecessary line breaks |
Greggers89 (talk | contribs) No edit summary |
||
| Line 9: | Line 9: | ||
*Web services<br> | *Web services<br> | ||
*Installers<br> | *Installers<br> | ||
*Packages<br> | |||
Depending on the LabVIEW version you have one or more of the above options might be missing. | Depending on the LabVIEW version you have one or more of the above options might be missing. | ||
Revision as of 00:13, 13 July 2019
Introduction
The application builder (AB) is a part of the LabVIEW Project environment, it has the possibilities to distribute your code in various ways:
- Executables
- DLLs
- Source distributions
- Web services
- Installers
- Packages
Depending on the LabVIEW version you have one or more of the above options might be missing.
Manual
 |
This article is a stub. You can help LabVIEW Wiki by expanding it. Please improve this article if you can. |
Advanced
The application builder has several interesting advanced uses
Automatic building
You can use a VI inside vi.lib that can build without user interaction. The VI is located in <vi.lib>\AppBuilder\BuildTargetBuildSpecification.vi. This VI takes a project path and optionally a build and target name as parameters.
Symbolic paths
Inside the application builder LabVIEW uses several symbolic paths to have envorinment 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 |