|
|
|
abld command syntax overview 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.
Note that, for certain abld commands, not all the
parameters— platform, build and
program—apply. For example, abld export
does not take these parameters, as exports do not depend on any of build,
platform or program.
Possible commands are as follows:
|
Possible options are as follows:
|
Note also that not all the options apply for all the commands. Where they do apply, they can be specified in either their long or abbreviated forms. For example,
-keepgoing (long form)
or
-k (abbreviated form)
This specifies the target platform. Possible platforms are:
|
If platform is not specified, or is specified as
all, then abld will carry out the specified command
for all the platforms specified in the component description file.
Basenames of .mmp files or extension makefiles must not
be platform names.
This specifies the build type. Possible types are:
|
If build is unspecified, or specified as
all, then abld will carry out the specified command
for both builds: udeb and then 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 unspecified, the specified command will be carried out for all projects within the component.
Where test is specified before command, the
command will operate on all the projects defined by
.mmp files listed in the prj_testmmpfiles section of
the component description file, rather than those projects defined by
.mmp files listed in the prj_mmpfiles section.
Note that the test parameter is irrelevant for some commands and, in those cases, cannot be specified.