Application Builder: Difference between revisions
m SouthPaw moved page Application builder to Application Builder: Capitalization of "Builder" |
m removed unnecessary line breaks |
||
| Line 1: | Line 1: | ||
{{TOCnestright}} | {{TOCnestright}} | ||
= Introduction = | |||
The application builder (AB) is a part of the LabVIEW Project environment, it has the possibilities to distribute your code in various ways:<br> | The application builder (AB) is a part of the LabVIEW Project environment, it has the possibilities to distribute your code in various ways:<br> | ||
| Line 11: | Line 10: | ||
*Installers<br> | *Installers<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. | ||
= Advanced | = Manual = | ||
{{Stub}} | |||
= Advanced = | |||
The application builder has several interesting advanced uses<br> | The application builder has several interesting advanced uses<br> | ||
== Automatic building | == Automatic building == | ||
You can use a VI inside vi.lib that can build without user interaction. The VI is located in <span style="font-style: italic;"><</span>''vi.lib>\AppBuilder\BuildTargetBuildSpecification.vi''. This VI takes a project path and optionally a build and target name as parameters.<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;"><</span>''vi.lib>\AppBuilder\BuildTargetBuildSpecification.vi''. This VI takes a project path and optionally a build and target name as parameters.<br> | ||
== Symbolic paths | == Symbolic paths == | ||
Inside the application builder LabVIEW uses several symbolic paths to have envorinment dependent variables. | Inside the application builder LabVIEW uses several symbolic paths to have envorinment dependent variables. | ||
{| cellspacing="1" cellpadding="1" border="1" style="width: 708px; height: 104px;" | {| cellspacing="1" cellpadding="1" border="1" style="width: 708px; height: 104px;" | ||
| Line 39: | Line 33: | ||
| NI_AB_PROJECTNAME<br> | | NI_AB_PROJECTNAME<br> | ||
| Name of the project<br> | | Name of the project<br> | ||
| Automatically place the build in a folder that is named after the project | | Automatically place the build in a folder that is named after the project | ||
|- | |- | ||
| NI_AB_TARGETNAME<br> | | NI_AB_TARGETNAME<br> | ||
| Line 45: | Line 39: | ||
| <br> | | <br> | ||
|} | |} | ||
[[Category:Building executables]] | [[Category:Building executables]] | ||
Revision as of 08:08, 11 January 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
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 |