Build Results Properties

Note:

Mobile Designer does not use this property for platforms that do not use JAR files, for example, iOS and Android.

If you are building your application for a platform that does use JAR files, be sure to set the property to a packager that creates JARs that the devices in your project can run. Some devices might not be able to execute JARs created by some packagers.

Platforms	All
Value	Specify one of the following values:
	Value	Meaning
	jar	Mobile Designer uses the built-in JAR packager that is part of the JDK.
	zip	Mobile Designer provides compression with WinZip.
	7zip	Mobile Designer provides compression with 7Zip. To create the JAR Mobile Designer uses the following command-line parameters when executing 7Zip: ${packager.7zip.args1} "filename" * ${packager.7zip.args2} The packager.7zip.args1 and packager.7zip.args2 properties are defined in the bs-defaults.xml file, which is in the following location: Mobile Designer_directory /Tools/Build/BuildScript/v1.0.0/bs-defaults.xml The following shows the default property settings in the bs-defaults.xml file: <property name="packager.7zip.args1" value="a -r -tzip"/> <property name="packager.7zip.args2" value="-mx=9 -mfb=255"/>
	kzip	Mobile Designer provides compression with Kzip. To create the JAR Mobile Designer uses the following command-line parameters when executing Kzip: ${packager.kzip.args} "filename" * The packager.kzip.args property is defined in the bs-defaults.xml file. The following shows the default property setting in the bs-defaults.xml file: <property name="packager.kzip.args" value="-r -zl121"/>
Default	kzip If you do not have the KZip packager installed, at run time Mobile Designer uses 7Zip.

Platforms

All

Value

true to skip the build.

Mobile Designer performs all the resource handling and cross-compiling (for platforms that require it), but does not compile the final binary.

Important:

When you set this property to true, be sure to select Retain output build files in the Multi Build dialog. When you select Retain output build files, Mobile Designer retains the cross-compiled code it generated from your original mobile code, along with any project (for example, Xcode project for iOS) it might have generated. You can then use the retained files and the native platform tools to compile to create the final binary.

false to have Mobile Designer perform the build step to compile and create the final binary.

Mobile Designer performs all the resource handling, cross-compiling, and compiles the final binary.

Default

false

Platforms

All

Value

File name format that you define by specifying one or more of the parameters listed below. At run time, Mobile Designer replaces the parameters with the values listed below.

@PROJECT@

is replaced with: ${project.jar.name}

@LANGPROJECT@

is replaced with: ${project.jar.name.selected-langgroup}, if it exists, otherwise replace with the value of ${project.jar.name}

@HANDSET@

is replaced with: ${mobiledesigner.handset.devicegroup.output.filename}

@LANGGROUP@

is replaced with: Selected language group

@VMAJOR@

is replaced with: X part of the project version number (X.y.z) that you specify in the Multi Build dialog when building the project.

@VMINOR@

is replaced with: Y part of the project version number (x.Y.z) that you specify in the Multi Build dialog when building the project.

@VMICRO@

is replaced with: Z part of the project version number (x.y.Z) that you specify in the Multi Build dialog when building the project.

Example:

Note:

The resulting file name must contain only valid characters are alphanumeric (A-Z, a-z, 0-9), period (.), and hyphen (-).

Default

None.

Note:

You must specify this property for a project.

When specifying the property, replace device_name with the name of the device for which you want to override the JAR file name. You can find the device name in the Handset field of the Multi Build dialog. For example, to specify the property for the Apple iPhone 5 phone, use the following property, where the IOS_Apple_iPhone5 portion of the property name is the device name for the Apple iPhone 5 phone:

Platforms	All
Value	See the value for the project.jarname.format property
Default	No default. Mobile Designer uses the value of project.jarname.format for all devices that you do not specifically override using the project.jarname.format.override.device_name property.

Platforms	All
Value	Semicolon-separated list of all the builds that Mobile Designer created
Default	n/a

Platforms	All
Value	Folder name that you define by specifying the one or more of the parameters listed below. At run time, Mobile Designer replaces the parameters with the values listed below.
	Parameter	Replace with the value of
	@LANGGROUP@	${selected.langgroup}
	@PLATFORM@	${selected.platform}
	@TARGET@	${selected.target}
	Example: If you want Mobile Designer to store the output data in a project folder named “_temp_EFIGS_j2me-jar_release_” for an English, French, Italian, German, Spanish (EFIGS) release J2ME build, specify the following: <property name="project.output._temp_.folder" value="_temp_@LANGGROUP@_@PLATFORM@_@TARGET@_"/>
Default	project _temp_ folder If you do not set this property, Mobile Designer stores the output and compilation directories in a project _temp_ folder alongside the compiled binary.