Build options provide a way of passing configuration information to the build environment. You can define a build option to pass along compiler flags, or you can define a build option to specify the path to a specific compiler. For details of the build options see Dimensions Build Predefined Symbols in The Templating Language and Processor chapter of the Developer’s Reference.
Dimensions CM offers you several different ways to define build options.
From the Build Configuration
Define options at the build configuration level if you want the options to be available to all targets in that build, as well as to the Pre-Script, Post-Script, and Clean-Up Script. An example of this would be a particular search path.
From the Build Area
Define options at the build area level if you want the options to be available to all builds in that area. An example of this would be the name of the License Manager host.
From the Target
Define options at the target level when they are specific to a particular target. An example of this would be a debug or trace option.
Options defined during the process of creating a new target, or editing an old target, are actually defined at the transition level. Therefore, the options are available to any other target in the build configuration. In fact, you can easily attach the options defined for one target to a second target by selecting Reuse script from another target when you create the second target.
From the Run Build Wizard
Define options in the Run Build wizard if you want the options to apply only to that one execution of the build. An example of this would be to add an option to print the time of execution.