| |
|
|
|
General Parameters
The 4D Application Builder provides a number of options that are all available using specific XML keys.
Use the BUILD APPLICATION command (in the Tools theme) to set the location of the XML document containing your customized keys.
The XML theme commands allow you to process XML documents.
BuildApplicationName
- version 2004
- / Preferences4D / BuildApp / BuildApplicationName
Accepted values
Description
Name of the compiled file or built application. This name is limited to 27 characters, not counting the extension; up to 31 characters with a 4-character extension.
If this key is not used, the compiled file or application will use the name of the structure file.
Example
<Preferences4D> <BuildApp> <BuildApplicationName>MyApplication</BuildApplicationName> </BuildApp> </Preferences4D>BuildWinDestFolder
- version 2004
- / Preferences4D / BuildApp / BuildWinDestFolder
Accepted values
Description
File access path of the Windows destination. If this key is not used, the location of the structure file will be used. The path can be fixed or relative to the structure file.
See also: BuildMacDestFolder
BuildMacDestFolder
- version 2004
- / Preferences4D / BuildApp / BuildMacDestFolder
Accepted values
Description
File access path of the Mac OS destination. If this key is not used, the location of the structure file will be used. The path can be fixed or relative to the structure file.
See also: BuildWinDestFolder
DataFilePath
- version 2004.4
- / Preferences4D / BuildApp / DataFilePath
Accepted values
Data file name and access path.
Description
Data file pathname of the final application. The pathname set can be absolute or relative to the structure file (.4db). Three syntaxes are accepted:
You should choose the syntax depending on the platform that the final application will be running on.
If this key is not used or is invalid, on the initial startup of the final application, 4D will look for the data file next to the structure file and, if it does not find it, will display a standard open file dialog box so that the user can indicate its location.
BuildCompiled
- version 2004
- / Preferences4D / BuildApp / BuildCompiled
Accepted values
Description
If this key is set to True, a compiled file is built.
If this key is not passed or if it is set to False, the compiled file is not built.See also: BuildApplicationSerialized
BuildApplicationSerialized
- version 2004
- / Preferences4D / BuildApp / BuildApplicationSerialized
Accepted values
Description
If this key is set to True, an application merged with 4D Volume Desktop using a 4D Volume Desktop (complete) serial number is built.
If this key is not passed or is set to False, the "Pro" merged application is not built.If no file access path is set using the RuntimeVLWinFolder or RuntimeVLMacFolder keys (depending on the operating system used for the build), or if the file access path is invalid, an error is returned and the current project build is stopped.
See also: BuildCompiled
ArrayExcludedPluginName
- version 2004
- / Preferences4D / BuildApp / ArrayExcludedPluginName
Accepted values
Description
By default, all plug-ins present in the Plugins folder are integrated into the built application. It is nevertheless possible to set a list of plug-ins to be excluded when building the application using this key.
This key is used to set the list of plug-ins to be excluded based on their names (plug-in names are unique).
You can also set a list of plug-ins to be excluded based on their numbers using the ArrayExcludedPluginID key.
See also: ArrayExcludedPluginID
ArrayExcludedPluginID
- version 2004
- / Preferences4D / BuildApp / ArrayExcludedPluginID
Accepted values
Description
By default, all plug-ins present in the Plugins folder are integrated into the built application. It is nevertheless possible to set a list of plug-ins to be excluded when building the application using this key.
This key is used to set the list of plug-ins to be excluded based on their ID (number). Plug-in IDs are shown on the "Plug-ins" page of the Application builder. You can also find the plug-in ID in its 4BNX resource.
You can also set a list of plug-ins to be excluded based on their names using the ArrayExcludedPluginName key.
See also: ArrayExcludedPluginName
IncludeAssociatedFolders
- version 11
- / Preferences4D / BuildApp / IncludeAssociatedFolders
Accepted values
Description
This key corresponds to the "Include related folders" option on the Compiled structure page of the Application builder. When this key contains the value True, the Plugins, Resources and Components folders located next to the structure are copied next to the compiled structure.
BuildComponent
- version 11
- / Preferences4D / BuildApp / BuildComponent
Accepted values
Description
If this key is set to True, a folder named "Components" will be created within the destination folder. It will contain the compiled structure included in a package suffixed ".4dbase", ready for installation as a component. If any, Resources and Extras folders that are associated to the original structure are placed in the "Components" folder as well.
See also: BuildCompiled, ArrayExcludedComponentName
ArrayExcludedComponentName
- version 11
- / Preferences4D / BuildApp / ArrayExcludedComponentName
Accepted values
Description
By default, all components present in the Components folder of the original structure are integrated into the built application. It is nevertheless possible to set a list of component names to be excluded when building the application using this key.
See also: BuildComponent, ArrayExcludedPluginName
 4D S.A. http://www.4D.fr Tel : 33 (1) 40 87 92 00 Fax : 33 (1) 40 87 92 01 e-mail : info@4d.fr |
| |
|
|
|