D.1 PM/CB (Intersolv Configuration Builder and PolyMake)

omake is highly compatible with PolyMake up to v4.0PM/CB Compatibility and with Intersolv PVCS Configuration Builder, to v5.1. omake supports all PM/CB macros and transformation macros, library object modules, local input scripts, and most directives.

System Macros

omake supports the PolyMake/Configuration Builder system macros listed in Table 25:

Transformation Macros

omake supports PM/CB v5.x, both long and one-letter names. When an omake equivalent exists, it is listed in the right column of Table 26. Note that PM/CB macros work on text; omake modifiers work on a macro, which is expanded into text and modified. To use the omake equivalent, you need to define macro name with value text.

Built-In Functions

In conditional expressions omake accepts:

%status

This is the exit status of last build script. It is the same as $(status) in omake.

Built-In Operations (Percent Directives)

%exit [ status ]

This directive terminates the make process with exit status (0 if status isn't given). Before terminating, the .DEINIT and .EPILOG special targets are run if they are defined. .DEINIT is run only if .INIT was run.

Directives

omake supports most PM/CB directives. For read-time interpretation, the directive starts in the first column of the makefile. For run-time interpretation, PM/CB emulation must be chosen and the directive must be indented.

Table 27 provides short descriptions of the supported directives.

Reserved Targets

omake supports the following PM/CB reserved targets:

.DEINIT [ : ]

If the .INIT special target was used, the build scripts of the .DEINIT target are executed immediately before the build scripts of .EPILOG are executed.

.EPILOG [ : ]

The same as the omake .AFTER special target. If emulating PM/CB, omake looks only for .EPILOG. Otherwise, it looks for .AFTER, and then .EPILOG.

.INIT [ : ]

This target's build scripts are executed immediately before any other build scripts.

.PROLOG [ : ]

The same as the omake .BEFORE special target. If emulating PM/CB, omake looks only for .PROLOG. Otherwise, it looks for .BEFORE, and then .PROLOG.

Local Input Scripts

omake accepts the PM/CB response file syntax:

target :
command [ prolog ] <X<[ text ]
build script
.
.
.
< [ epilog ]

where X is a single character, usually @. If text is given, it is copied to the response file. Each build script is then copied to the response file. The command syntax is

command prolog Xtempfile epilog

where tempfile is a temporary file with a name of the form makenum.rsp

Operation-Line Modifiers

omake supports all PM/CB operation-line modifiers, which are listed in Table 28.

PM/CB Emulation

omake is highly compatible with PM/CB, but there are differences in how they read makefiles and in how they run. In PM/CB emulation mode,omake operates like PM/CB.

Emulation at Startup Time

If PM/CB emulation mode is selected at startup time, omake emulates the PM/CB command line and selection of the built-ins file. Selection of PM/CB emulation at startup time is done with the -EP flag, either on the command line or in the OMAKEOPTS environment variable.

To determine the startup emulation mode, omake examines the OMAKEOPTS environment variable for -Ex flags. It then examines the command-line for -Ex flags. If the last -Ex flag is -EP, omake starts up emulating PM/CB.

Emulation After Startup Time

The .POLY_MAKE directive turns on PM/CB emulation mode from the point it appears in the initialization file or any makefile.

The Command Line

First the OMAKEOPTS environment variable is parsed for options. Then, if omake is emulating PM/CB at startup, the MAKEOPTS and BUILD environment variables are parsed for options. Then the command line is parsed. Parsing entails the following:

• Handling the case-insensitivity of the PM/CB command line.

• Mapping options into omake equivalents. The help screen switches to the options available with our emulation of PolyMake v4.0 and Configuration Builder v5.x. The help screen's contents are stored in the file omhelp.cb.

• Handling the long-named Configuration Builder v5.x options.

• Warning about unconvertible command-line options.

Without emulation at startup, the command line is as documented in the section Command-Line Options.

The Emulation File (BUILTINS.CB)

If omake is emulating PM/CB at startup, omake reads its internal rules and macros. It then looks for builtins.cb first in the directory of make.ini, in the directory of omake.exe, and along directories of the INIT environment variable, in that order. If builtins.cb is found, it is read for macros and rules that give more complete PM/CB emulation.

The Initialization File (TOOLS.INI)

PM/CB distinguishes between an initialization file and a built-ins file. Both contain initialization information. The initialization file is almost always the file named tools.ini. If omake is emulating PM/CB at startup, omake searches for the initialization file and reads the first one it finds :

1. Named by the -Init command-line option

2. Named tools.ini in the current directory

3. Named tools.ini in a directory named by the INIT environment variable

If omake finds the initialization file, it reads information in the file starting with the section heading [PVCS.

The BUILTINS File

If omake is emulating PM/CB at startup, omake searches for the built-in file, and reads the first one it finds:

1. Named by the -b command-line flag

2. Named builtins in the current directory

3. Named builtins.mak in the current directory

4. Named by the BUILTINS environment variable

If omake is not emulating PM/CB at startup, it uses the method documented in the section Locating the Initialization File to locate the initialization (built-ins) file.

The Makefile

If omake is emulating PM/CB at start up, omake looks for the default makefile in this order: script.bld, script, makefile, makefile.mak. The first file found is read. When trying to read a makefile file that doesn't have an extension, omake tries file, file.bld, and file.mak, in that order.

Makefile Contents

If omake is emulating PM/CB:

• The line continuation character sequence \<ENTER> is removed from the input.

• The ^ character is used for quoting and produces the following effects:

Character	Effect
^^	literal ^
^<ENTER>	literal newline
^$	literal $
^\	literal \
^#	literal #

• The PM/CB-compatible directives listed in the previous section can be used at run time as well as read time.

• The %end directive is the same as %endif. Without emulation, %end terminates a %foreach or %while directive.

• .INCLUDE file searches only the current directory.

• Makefile macro names are case-sensitive.

• The =+ macro (prepend) definition is supported.

• Environment variables override built-in macro definitions.

• The MFLAGS macro is the same as _FlagsMacros.

• The TMP, TEMP, and WORK environment variables are tried, in order, for the location of the directory where temporary files are created. Without emulation, omake uses the value of the MAKE_TMP macro.

• Duplicate entries in a target's dependencies are allowed. Without emulation, omake removes duplicate dependencies.

Operation Lines (Build Scripts)

If omake is emulating PM/CB:

• The shell program is used for executing every build script. The * and (NoShell) prefixes suppress execution of the shell program for this build script.

• The build scripts cd dir and chdir dir both change to directory dir and stay there until changed back explicitly. Otherwise, omake starts each build script from the directory that omake started in the $(MAKEDIR) directory.

• The : modifier means swap out of memory and * means suppress shell. Without emulation, * means swap out and : means suppress shell.

• The - shell-line prefix does not print the Error code ... (ignored) message.

Unsupported PM/CB Features

When running PM/CB makefiles with omake, be aware of the lack of support for some PM/CB features. The list here provides a workaround, when it is available.

Unimplemented Directives and Reserved Targets

Iteration Groups

An iteration group does an implicit iteration over the $? macro. For example:

test.lib : test.obj chart.obj input.obj
{
lib contract.lib -add $? omake m2 noask
}

The %foreach directive can be used in its place:

test.lib : test.obj chart.obj input.obj
%foreach file in $?
lib contract.lib -add $(file) omake m2 noask
%endfor

Suffix Dependencies

Suffix dependencies allow the specification of a set of suffixes to be tried when building a particular target. This is not supported by omake.

Command-Line Flags

The following PM/CB command-line flags are not supported: -Batch, -C, -Compile, -NoEnvInherit, or -Rebuild.

Makefile Contents

The ~ suffix on archive extensions to handle like-named files in different directories is not supported. Instead, use a pattern-matching rule , such as this:

%.c : c:/apps/archives/%.c
get -q -w $(_SourceRev) $(_Source)($(_Target))

The _DefaultSuffixes system macro is not supported.

Shared Definitions

omake does not parse the PVCS Version Manager configuration file automatically.

Operation-Line Modifiers

For PM/CB, the (Always) operation-line modifier (Shell-Line Modifiers) overrides the -Touch flag. This is not supported in omake. You can use the .MAKE attribute instead. For example:

# PM/CB
recursive :
(Always)$(MAKE) $(MAKEFLAGS)

# Omake
recursive .MAKE :
$(MAKE) $(MAKEFLAGS)

Built-In Operations

The built-in operations that handle foot printing are not supported. These operations are %EAStamp, %ExeStamp, and %ObjStamp.