Application Builder - Revision history

Q: Added some to the page and added links.

2024-03-19T00:58:46Z

Added some to the page and added links.

← Older revision		Revision as of 00:58, 19 March 2024
Line 1:		Line 1:
	{{TOCnestright}}		{{TOCnestright}}

	~~= Introduction =~~		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>~~

	*~~Executables<br>~~		* [[Build Specification/Application (EXE)\|Application (EXE)]]
	*~~DLLs<br>~~		* [[Build Specification/Installer\|Installer]]
	*~~Source distributions<br>~~		* [[Build Specification/.NET Ineterop Assembly\|.NET Ineterop Assembly]]
	*~~Web services<br>~~		* [[Build Specification/Package\|Package]]
	*~~Installers<br>~~		* [[Build Specification/Packed Library\|Packed Library]]
	*~~Packages<br>~~		* [[Build Specification/Shared Library (DLL)\|Shared Library (DLL)]]
			* [[Build Specification/Source Distribution\|Source Distribution]]
			* [[Build Specification/Zip File\|Zip File]]

	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.

	= ~~Manual~~ =		== Build Specification Dialog ==
	~~{{Stub}}~~		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.
	~~= Advanced~~ =

	~~The application builder has several interesting advanced uses<br>~~		See [[Build Specification dialog]].

	== ~~Automatic building~~ ==		== Application Builder API ==
	~~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>~~		An API for the Application Builder is available and can be found in the [[Functions Palette/Programming/Application Control/Application Builder\|Application Builder Palette]].

	== 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 environment-dependent variables.

	{\| ~~cellspacing~~="~~1" cellpadding="1" border="1" style="width: 708px; height: 104px;~~"		{\| class="wikitable"
	\|-		\|-
	! scope="col" \| Symbolic path<br>		! scope="col" \| Symbolic path<br>

Greggers89 at 00:13, 13 July 2019

2019-07-13T00:13:32Z

← Older revision		Revision as of 00:13, 13 July 2019
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.

MichaelAivaliotis: removed unnecessary line breaks

2019-01-11T08:08:25Z

removed unnecessary line breaks

← Older revision		Revision as of 08:08, 11 January 2019
Line 1:		Line 1:
	{{TOCnestright}}~~<br>~~		{{TOCnestright}}

	~~= Introduction<br> =~~

			= 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.~~<br>~~		Depending on the LabVIEW version you have one or more of the above options might be missing.

	~~<br>~~

	~~= Manual<br> =~~

	~~{{Stub}}<br>~~

	= Advanced~~<br>~~ =		= Manual =
			{{Stub}}
			= Advanced =

	The application builder has several interesting advanced uses<br>		The application builder has several interesting advanced uses<br>

	== Automatic building~~<br>~~ ==		== 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~~<br>~~ ==		== Symbolic paths ==

	Inside the application builder LabVIEW uses several symbolic paths to have envorinment dependent variables.~~<br>~~		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~~<br>~~		\| 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>
	\|}		\|}

	~~<br>~~

	~~<br>~~

	~~<br>~~

	[[Category:Building executables]]		[[Category:Building executables]]

Bryan: SouthPaw moved page Application builder to Application Builder: Capitalization of "Builder"

2019-01-10T15:24:34Z

SouthPaw moved page Application builder to Application Builder: Capitalization of "Builder"

← Older revision	Revision as of 15:24, 10 January 2019
(No difference)

Adnan-Sozuan: /* Symbolic paths */

2010-11-17T10:49:02Z

Symbolic paths

← Older revision		Revision as of 10:49, 17 November 2010
Line 29:		Line 29:
	== Symbolic paths<br> ==		== Symbolic paths<br> ==

	Inside the application builder LabVIEW uses several symbolic paths to have envorinment dependent variables.<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;"		{\| cellspacing="1" cellpadding="1" border="1" style="width: 708px; height: 104px;"
	\|-		\|-
	! scope="col" \| Symbolic path<br>		! scope="col" \| Symbolic path<br>
	! scope="col" \| Contents<br>		! scope="col" \| Contents<br>
	! scope="col" \| Usage<br>		! scope="col" \| Usage<br>
	\|-		\|-
	\| 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<br>		\| Automatically place the build in a folder that is named after the project<br>
	\|-		\|-
	\| NI_AB_TARGETNAME<br>		\| NI_AB_TARGETNAME<br>
	\| Name of the (Real-Time) target<br>		\| Name of the (Real-Time) target<br>
	\| <br>		\| <br>
	\|}		\|}

	<br>		<br>

	<br>		<br>

	<br>		<br>

	[[Category:~~Building_executables~~]]		[[Category:Building executables]]

Tcplomp: Automatic build

2010-08-09T07:13:28Z

Automatic build

← Older revision		Revision as of 07:13, 9 August 2010
Line 1:		Line 1:
	{{TOCnestright}}<br>		{{TOCnestright}}<br>

	= Introduction<br> =		= Introduction<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>		The application builder (AB) is a part of the LabVIEW Project environment, it has the possibilities to distribute your code in various ways:<br>

	*Executables<br>		*Executables<br>
	*DLLs<br>		*DLLs<br>
	*Source distributions<br>		*Source distributions<br>
	*Web services<br>		*Web services<br>
	*Installers<br>		*Installers<br>

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

	<br>		<br>

	= Manual<br> =		= Manual<br> =

	{{Stub}}<br>		{{Stub}}<br>

	= Advanced<br> =		= Advanced<br> =

	The application builder has several interesting advanced uses~~, for instance it can be used for automatic building.~~ <br>		The application builder has several interesting advanced uses<br>

	<br>		== Automatic building<br> ==

	=~~= Symbolic paths~~<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>

	Inside the application builder LabVIEW uses several symbolic paths to have envorinment dependent variables.<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;"		{\| cellspacing="1" cellpadding="1" border="1" style="width: 708px; height: 104px;"
	\|-		\|-
	! scope="col" \| Symbolic path<br>		! scope="col" \| Symbolic path<br>
	! scope="col" \| Contents<br>		! scope="col" \| Contents<br>
	! scope="col" \| Usage<br>		! scope="col" \| Usage<br>
	\|-		\|-
	\| 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<br>		\| Automatically place the build in a folder that is named after the project<br>
	\|-		\|-
	\| NI_AB_TARGETNAME<br>		\| NI_AB_TARGETNAME<br>
	\| Name of the (Real-Time) target<br>		\| Name of the (Real-Time) target<br>
	\| <br>		\| <br>
	\|}		\|}

	<br>		<br>

	<br>		<br>

	<br>		<br>

	[[Category:~~Building executables~~]]		[[Category:Building_executables]]

Tcplomp: New page: {{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:
...

2010-08-09T07:06:40Z

New page: {{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: ...

New page

{{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: 

*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 =

{{Stub}} 

= Advanced =

The application builder has several interesting advanced uses, for instance it can be used for automatic building. 

 

== Symbolic paths ==

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;"
|-
! scope="col" | Symbolic path 
! scope="col" | Contents 
! scope="col" | 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 
| 
|}

 

 

 

[[Category:Building executables]]