For calling bmk (from the command line), here's what the user guide says:
In addition, there are some undocumented ones that you can find out by studying at bmk source. For example, I think -g (target architecture - x86 or ppc) is for both makeapp and makemods.
Makemods
The makemods operation builds a set of modules.
Makemods takes one optional argument: a module filter. This can be a module scope name (to build a subset of modules) or a fully qualified module name (to build an individual module). If the module filter is omitted, than all module are built.
Valid options for makemods are:
Option Effect
-d Build debug version. By default, both debug and release versions are built.
-r Build release version. By default, both debug and release versions are built.
-a Build all modules regardless of timestamps. By default, only modules that have been modified are built.
Some examples of makemods in action:
bmk makemods mymods
bmk makemods -a mymods.testmod
The makemods operation builds a set of modules.
Makemods takes one optional argument: a module filter. This can be a module scope name (to build a subset of modules) or a fully qualified module name (to build an individual module). If the module filter is omitted, than all module are built.
Valid options for makemods are:
Option Effect
-d Build debug version. By default, both debug and release versions are built.
-r Build release version. By default, both debug and release versions are built.
-a Build all modules regardless of timestamps. By default, only modules that have been modified are built.
Some examples of makemods in action:
bmk makemods mymods
bmk makemods -a mymods.testmod
In addition, there are some undocumented ones that you can find out by studying at bmk source. For example, I think -g (target architecture - x86 or ppc) is for both makeapp and makemods.