RADE

Purpose

The mkmk command builds sources written in C, C++, Express, Fortran, JAVA.

If you use another language, please contact Dassault Systèmes for the integration of your language in the CAA Workbench product.

[Top]

Default Usage

Run without any option, mkmk by default executes the four following phases:

• "ID card compilation": processes the [container] framework ID card
• "header list generation": produces the list of headers made public by the [container] framework. Corresponding file is <fw_name>/various/$MkmkOS_VAR/Public<fw_name>.lh
• "Imakefile.mk checking": the Imakefile.mk  are checked and update module if necessary. For updating, see -u, -g or -dev options.
• The build itself. When processing a shared library, mkmk splits the phase in two, in order to successfully build a series of them:
  • forced standalone generation of the (shared) library, even when symbols are missing
  • generation of the shared library (not OK if symbols are missing).

[Top]

Usage

mkmk -h

to consult the usage of the command

mkmk [-showcmd] [-jobs <nbproc>] [-noci | -idcard] [-u | -nomk] [-w | -g | -dev] [-mkdataonly] [-nobuild] [-bsc] [-a | <FW1> [<FW2>...] | <Mod> [<Mod2>...] | <Fw/Mod>] | -lFW /path/FWlst [-lMod /path/Modlst] ]

internal usage

-jobs <nbproc>

Multiprocessing mode. nbproc is the maximum number of parallel tasks mkmk forks

-showcmd

Prints command lines before to executing them.

-noci

Does not intend to recompile the (embedding) framework identity card. This is not the default.

-idcard

Intend to recompile only the (embedding) framework identity card. No module are built. This is not the default.

-u

Forces the update of the build time data.

-w

Compilations with warning messages.

-g

Compilations in debug mode.

-dev

Disables the optimized mode at compile-time.

-nomk

Deactivates the Build Time update. 

-mkdataonly

Only regenerates the Build Time data.

-nobuild

Does not start the build. Useful when coupled with option -u. mkmk then only regenerates the Build Time data.

To specify what target to process:

[nothing]

when in a module directory, mkmk processes current module

-a

mkmk processes data under current position in the file system:

• when in a work space root directory: every framework (and embedded modules).
• when in a framework directory: every module in current framework.

<FW1> [<FW2>...]

all the modules in the (list of) framework(s),

-lFW /path/FWlst

all the modules in the specified list of framework(s).

-lMod /path/Modlst

all the modules in the specified list of module(s), which belong to the current framework.

<Mod> [<Mod>...]

all the modules in the list, which belong to current framework.

The table hereunder gives you a view on what could be used:

[Top]

Examples

Beginners: if you are not (yet) familiar with the make principles, we recommend you to use:

mkmk

1. The list of header files exported by the framework is updated.

2. The identity card of the framework is updated if needed.

3. The Build Time Data  is updated if needed.

4. The dependencies between derived objects and source objects are recomputed.

5. The derived objects which set of dependencies changed, or for which at least one prerequisite changed, are rebuilt.

[Top]

History

Copyright © 2000, Dassault Systèmes. All rights reserved.