prj_mmpfiles
prj_mmpfiles
mmp_file_1
[tidy]
mmp_file_1
[tidy]
makefile
makefile_1
[tidy]
makefile
makefile_n
[tidy]
In the prj_mmpfiles
section,
list the .mmp
files contained in your component.
Specify each .mmp
file on a separate line.
If a relative path is specified with an .mmp
file,
the path will be considered relative to the directory containing the
bld.inf
file.
For example, if in the prj_mmpfiles
section,
a certain Hello.mmp
file is specified as a relative path:
PRJ_MMPFILES
ProjSpec\Hello.mmp
and if the bld.inf
file is in \MyComp\
,
then the full path for the location of Hello.mmp
will
be \MyComp\ProjSpec\Hello.mmp
.
Specify the tidy
attribute if
the releasable that an .mmp
file defines is purely internal to
your component, and therefore not required either by other components or for
your component to execute.
If the tidy attribute is specified in your component’s
description file, then this will indicate to the abld
tool when it
is used to run the command abld tidy
, to
remove those releasables that are no longer required.
Use keyword makefile
to specify
an extension makefile for your component. Extension makefiles can be used where
build activities need to be carried out which are not catered for by generated makefiles.
Build activities relating to particular .mmp
files
or extension makefiles are carried out in the order in which the
.mmp
files and extension makefiles are listed in the
bld.inf
file. Extension makefiles can be interspersed among the
.mmp
files.
See Extension makefiles for more details.
The prj_mmpfiles
section is
preprocessed for each platform listed in the prj_platforms
section.
If an .mmp
file or extension makefile applies only
to a particular platform, then place the item within
#if defined <identifier>
#endif
For example, if an .mmp
file relates only to the WINS platform,
specify the file as follows:
#if defined(WINS)
<mmp_file>
#endif