abld command syntax overview in abld command syntax

The abld batch file is used to control all aspects of building a project. The batch file is created using bldmake from a component description file.

abld [ test ] command [ options ] [ platform [ build [ program ] ] ]

A summary of command, options, platform, build, program and test are given below.

You can use the following commands with abld:

`build`	Combines the commands `export`, `makefile`, `library`, `resource`, `target`, and `final`.
`clean`	Removes everything built with `abld target`.
`cleanexport`	Removes files created by `abld` `export`.
`export`	Copies the exported files to their destinations.
`final`	Allows extension makefiles to execute final commands.
`freeze`	Freezes exported functions in a `.def` file.
`help`	Displays commands, options, or help about a particular command.
`library`	Creates import libraries from the frozen `.def` files.
`listing`	Creates an assembler listing file for a particular source file.
`makefile`	Creates makefiles or IDE workspaces.
`reallyclean`	Removes files similar to the `clean` command, and additionally removes exported files and makefiles.
`resource`	Creates resources files and bitmaps.
`target`	Creates the main executable file and also the resources.
`tidy`	Removes executable files which need not be released.

You can use the following options with abld:

`-check or -c`	Checks whether the filenames of executables and resource files are compatible for Linux builds.
`-debug`	Generates symbolic debug information for release or debug builds.
`-keepgoing or -k`	Builds unrelated targets on error.
`-no_debug`	Does not generate symbolic debug information for release or debug builds.
`-savespace or -s`	Deletes intermediate files on success.
`-verbose or -v`	Displays tools calls as they happen.
`-what or -w`	Lists all releaseables, which includes executables/map files, resource files and so on.
`-i <platform>`	Specifies the ARM target to build for, overriding other settings.
`-invariant or -inv`	Marks all DLLs without `FEATUREVARIANT` keyword in the MMP file as invariant across all feature variant builds. If this option is not specified, all DLLs are considered to be different in all feature variant builds.

This specifies the target platform. Possible platforms are:

Build target	Purpose
`all`	Builds for all platforms.
`armv5`	Builds for ABI v1 for ARMV5 architecture, using ARM RVCT compiler.
`armv5_abiv2`	Builds for ABI v2 for ARMV5 architecture, using ARM RVCT compiler.
`armv6`	Builds for ABI v2 for ARMV6 architecture, using ARM RVCT compiler.
`armv6t2`	Builds for ABI v2 for ARMV6 architecture supporting Thumb-2 instruction set, using ARM RVCT complier.
`armv7a`	Builds for ABIv2 for ARMv7 architecture supporting Thumb-2 instruction set, using ARM RVCT complier.
`cw_ide`	Builds Metrowerks CodeWarrior project (importable `.xml` file).
`gcce`	Builds for ABI v2 for ARMV5 architecture, using GNU GCC compiler.
`gccev6`	Builds for ABI v2 for ARMV6 architecture, using GNU GCC compiler.
`gccev6t2`	Builds for ABI v2 for ARMv6 architecture supporting Thumb-2 instruction set, using GNU GCC compiler.
`gccev7a`	Builds for ABI v2 for ARMV7 architecture supporting Thumb-2 instruction set, using GNU GCC compiler.
`gccxml`	Generates the XML description of the project and the program, using GCC XML.
`vs6`	Creates project files suitable for opening the project in Microsoft Visual Studio IDE, version Visual C++ v6.
`vs2003`	Creates project files suitable for opening the project in Microsoft Visual Studio IDE, version .NET2003.
`winscw`	Builds for Symbian OS emulator on Microsoft Windows, using Metrowerks CodeWarrior compiler.

If platform is not specified, or is specified as all, then abld will build for all the platforms specified in the component description file.

Basenames of .mmp files or extension makefiles must not be platform names.

If the platform.variant_name is specified, then abld will build a new variant for the specified platform.

For example, the following abld command builds the binary for a variant of ARMV5:

> abld build armv5.myvar

If the variant_name is default, then both the following commands will have the same effect.

> abld build armv5.default

> abld build armv5

This specifies the build type. Possible types are:

`udeb`	Debug build
`urel`	Release build
`all`	Debug and release builds

If build is not specified, or specified as all, then abld will build for both udeb and urel.

Basenames of .mmp files or extension makefiles must not be build type names.

This specifies the basename of a particular .mmp file or extension makefile, in order to limit the command to a single project within a component.

If program is not specified, then all the projects within the component are built.

If test is specified before command, the command will build all the projects defined by .mmp files listed in the prj_testmmpfiles section of the component description file, rather than those listed in the prj_mmpfiles section.

The platform, build, and program parameters are not applicable for certain abld commands.

For example, these parameters are irrelevant for export command, as it does not depend on them.
You can use -debug or -no_debug options irrespective of the output build type, that is, UREL or UDEB.
All options are not applicable to all the commands. Wherever applicable, they can be specified in their long or short forms. For example,

-keepgoing (long form)

or

-k (short form)
If the variant name is not specified along with the platform, the binary is built for the default configuration.
The test parameter is not relevant for some commands, and in those cases, it cannot be specified.
The build platforms ARMV5 and ARMV5_ABIv2 are applicable to Symbian OS versions earlier than 9.4. From Symbian OS v9.4 onwards, the build platforms ARMV5 and ARMV5_ABIv1 generates binaries and libraries conforming to ABIv2 and ABIv1 respectively.

`abld` command syntax overview

Invocation syntax

command

options

platform

build

program

test

Notes: