OpenMake Meister

How Build Methods are Executed

Build Methods are designed so that they contain no Target specific data.  The Build Methods are generic and use variables instead of hard coded values.  Build Methods are read by om and are translated into temporary build scripts.  These temporary scripts contain references to the actual Target information. At build time, the build gets the Target information from the Build Control File generated by bldmake.  The build also gets the Build Method from the Build Control File as it is appended to the bottom.  As the build occurs, om creates a temporary build script based on the Build Method script, and dependency and target information contained in the Build Control File. The temporary script contains all of the logic and specific file information that would normally be hard coded in a make or build.xml file.  This temporary "Target specific" build script is generated in the .submit directory under the build directory with a .pl extension. The script name is preceded by om and based on the Target name with restricted characters replaced with _.  

Example:

./submit/om_metalworks_jar.pl

*Note:  As an audit and debugging tool, you can pass om the -ks parameter.  This parameter forces om to "keep" the temporary script so that it can be viewed to determine if the variables have been set correctly.