OpenMake Meister

-a

Forces a clean all by making the dependencies to be newer than the target

None required

clean

Deletes all the target and intermediate targets from the file system

None required

clean all

Forces a full rebuild by deleting the targets and intermediate targets making the dependencies to be newer than the non-existent targets

None required

-b

Produces a Build Audit report in the build directory.  If the file name used end in .htm or .html it will get stored on the Knowledge Base Server.

File name for Bill of Material Report

(Recommended .htm or .html extension)

-c

Changes current working directory - allows you to change the directory of the build. 

Name of new build directory

-d

Tells om not to scan source - speeds up Build; Impact Analysis, Footprint or Build Audit Reports will be generated with only high level dependencies.

None required

-e

Creates a Footprint embedded in the executables

None required

-f

Tells om to use a Build Control File other than the default Build Control File name. 

Build Control File name.

-g

Performs Impact Analysis during the build.

Note: If used with -pt, only Impact Analysis will be done and no build will be executed.

None required

-i

(Lower case "I") This option allows for the use of a Perl script that defines the name and location of compilers to be called by the Command scripts.   When om executes it will attempt to locate the compiler based on the Perl script passed with this option. If it cannot locate the compiler, it will search the PATH for the compiler.  The Perl script containing the compiler information must be passed as a parameter and should include the following:

$Tools{"CL"} = "<fully qualified compiler location>";

Example:

$Tools{"CL"} = "c:\\program files\\vc98\\bin\\cl.exe";

$Tools{"VB6"}="c:\\program files\\vb6\\bin\\vb6.exe";

Name of the Perl script which contains the compiler information.

-j

Tells om not to scan the Java source. No Impact Analysis, Footprint or Build Audit report will be generated.

None required

-l

(Lower case “L”) Tells om to save a log and use the log name that is passed as a parameter.

Log file name

-ob

Used for building at the command line. Sends Log Output to the screen and to an HTML file stored on the KB Server.  Must use the following to specify the file name:

-ld  <yyyy-mm-dd hour_minute_second>

Note: You must specify your date and time. The command line does not use the actual system date and time. This date and time will be used to create your file name.

-lj  <job name>

-lm <machine name>

-lo <owner name>

Example:

om -ob -ld "2001-01-01 01_01_01" -lj "build demo Development" -lm LAB01 -lo MTOM04

Also, if the Build should be logged as public pass:

  -lp

-oh

Used when building at a command line.  Sends Build Log Output to an HTML file stored on the KB Server.  Must use the following to specify the log file name:

 -ld  <yyyy-mm-dd hour_minute_second>

Note: You must specify your date and time. The command line does not use the actual system date and time. This date and time will be used to create your file name.

-lj  <job name>

-lm <machine name>

-lo <owner name>

Example:

om -ob -ld "2001-01-01 01_01_01" -lj "build demo Development" -lm LAB01 -lo MTOM04

Also, if the Build should be logged as public pass:

-lp

-os

Sends Build Log Output to the screen only.

-ov

Runs om in verbose mode. This provides additional build log output.

None required

-ox

Creates an xml based log file.

log file name

-o

Runs om in verbose mode. This mode provides additional build log output.

None required

-rp

Retrieve Program.  This parameter is used to tell om to execute a script that will retrieve files from a version control tool. The file specified by this parameter will be executed before any dependency checking has occurred by om.  om locates the script file to execute by searching the Dependency Directory.

om -rp <script name>

Example:

om -rp getfiles.bat

<retrieve script file name>

-rc

Retrieve Configuration.  The contents of the file specified by this parameter are passed to the Retrieve Program (-rp) as parameters. This can be used provide a list of configuration information needed by the retrieve program such as log in ID, database name, etc.  om locates the configuration file by searching the Project Dependency Directories.

om -rp <script name> -rc <configuration file name>

Example:

om -rp getfiles.bat -rc configfile.txt

<configuration file>

-s

Preserves case sensitivity while scanning dependencies. Needed on UNIX when include files are coded with upper case.

None required

-t

Allows you to pass a Target Definition file to om to build the specified Target.

Target Name

-w

Creates MSVC Project Workspace.

None required

  -x

Stops build on compile or link error.

None required

 -v

Displays the version of om

None required

-?

Displays the usage statement

None required

<var>=<Var value>

Tells om to pass variable information to the Command scripts.  If customized scripts are written, variables can be defined and the value can be set when om executes.  om will then pass the value of the variable to the Scripts.  The following pre-defined Variables can be passed to the scripts via Workflows or the Command Line when executing om:

CFG = Release

CFG = Debug

Determines if Release or Debug flags are to be used.