The command line makefile generator can process the TPD file hierarchy generated by Eclipse and generate one or more Makefiles for these. There are three methods to generate Makefiles:
The command line makefile generator can process the TPD file hierarchy generated by Eclipse and generate one or more Makefiles for these. There are three methods to generate Makefiles:
. Generate a single Makefile that will contain all files from all projects. The following command line options can be used for this: `-t` `–b` `–D` `–P` `–V` `-W`. When using this method the –c switch should not be used because in this case all the files are seen as part of one large project.
. Generate a single Makefile that will contain all files from all projects.
. Generate a Makefile hierarchy recursively (-r): for each TPD file generate a Makefile that builds only one project but has a dependency on other projects using the feature called "central storage". This dependency relation in the Makefile means that prior to building a project all the other projects that it depends on must be built. The dependency relation is contained by the top-level project’s Makefile. For that to work the central storage (`-c` switch in the makefile generator) feature is used to avoid compiling the source files also in top level projects that have already been compiled in the sub-projects where they belong to. Using this one Makefile all the projects can be built in the proper order. The following command line options can be used for this: `-t` `–b` `–D` `–P` `–F` `–T` `–X` `–V` `-W` `-Z` `-H`.
The following command line options can be used for this: `-t` `–b` `–D` `–P` `–V` `-W`.
. Generate a Makefile hierarchy with improved linking method (`-Z`): for each TPD file generate a Makefile that builds only one project but has a dependency on other projects. It provides highly flexible way of linking static- and/or dynamic libraries together. The following command line options are obligatory `-`t `–Z` `–F` `–r` and these are optional: `–H` `–W`.
When using this method the –c switch should not be used because in this case all the files are seen as part of one large project.
. Generate a Makefile hierarchy recursively (-r):
When generating multiple Makefiles the working directories of each referenced project are determined by the TPD file of the project. The TPD file can contain more than one build configuration, but there’s always one active configuration. The active configuration is determined by the TPD file itself by the element `<ActiveConfiguration>`. Different build configurations can have different working directories and other settings. This can be overruled by the referencing project’s required configuration setting (via `<requiredConfiguration>` embedded into `<configurationRequirement>`) or in case of a top-level TPD by using the –b command line option. Both the Makefile and the symlinks to source files are generated into the working directory.
for each TPD file generate a Makefile that builds only one project but
has a dependency on other projects using the feature called "central storage".
If there is no "workingDirectory" specified in the TPD file, default directory will be created with name "bin". If more than one project define the same directory for working directory a collision can happen. This can be avoided by the command line switch –W (see below).
This dependency relation in the Makefile means that prior to building a project all the other projects
that it depends on must be built.
The dependency relation is contained by the top-level project’s Makefile.
For that to work the central storage (`-c` switch in the makefile generator) feature is used to avoid compiling the source files also in top level projects that have already been compiled in the sub-projects where they belong to. Using this one Makefile all the projects can be built in the proper order. The following command line options can be used for this: `-t` `–b` `–D` `–P` `–F` `–T` `–X` `–V` `-W` `-Z` `-H`.
. Generate a Makefile hierarchy with improved linking method (`-Z`):
for each TPD file generate a Makefile that builds only one project but has a dependency on other projects.
It provides highly flexible way of linking static- and/or dynamic libraries together.
The following command line options are obligatory `-t` `–Z` `–F` `–r` and these are optional: `–H` `–W`.
When generating multiple Makefiles the working directories of each referenced project are determined by the TPD file of the project.
The TPD file can contain more than one build configuration, but there’s always one active configuration.
The active configuration is determined by the TPD file itself by the element `<ActiveConfiguration>`.
Different build configurations can have different working directories and other settings.
This can be overruled by the referencing project’s required configuration setting (via `<requiredConfiguration>` embedded into `<configurationRequirement>`) or in case of a top-level TPD by using the –b command line option. Both the Makefile and the symlinks to source files are generated into the working directory.
If there is no "workingDirectory" specified in the TPD file, default directory will be created with name "bin".
If more than one project define the same directory for working directory a collision can happen.
This can be avoided by the command line switch –W (see below).
If you want to generate Makefiles from tpd files with incremental dependency (via .d files), you shall apply switch –g and you must not apply –m, in addition to these the top level project descriptor (tpd) file shall contain the element ordering incremental dependency as follows:
If you want to generate Makefiles from tpd files with incremental dependency (via .d files), you shall apply switch –g and you must not apply –m, in addition to these the top level project descriptor (tpd) file shall contain the element ordering incremental dependency as follows:
