The figure below shows the “Generation” tab of the project edition box, in which you can specify code generation options for the selected project.
The “Generation” tab of the project edition box
You can specify the following options:
Variant: The current variant utilized by the module for this project.
The default choice is the standard behaviour from C++ Designer’s resources path.
Type Library: The type library selected for the model elements manifested by the project.
Generated body files path: The root output directory for the body files produced by the target. A C++ code generation target produces body files for UML packages, classes and interfaces manifested by the project.
Generated header files path:The root output directory for the header files produced by the target. A C++ code generation target produces header files for UML packages, classes and interfaces manifested by the project.
Header files extension: The extension of the header files produced by the target.
Body files extension: The extension of the body files produced by the target.
Description: A description for the generation target. This will be visible in the model as a “description” note on the artifact.
Variants are used for advanced customization of the C++ Designer module.
The "Manage Variant" command opens the variant manager, used to install
new variants for the module, or uninstall existing variants.
The variant management box
1.: Opens a file chooser to install a new variant. You must select the variant directory itself, not the “act” or “product” directory.
2.: Removes the selected variant from the project. Obviously, it is impossible to delete the standard behaviour.
3.: Displays all variants available in this project.
4.: The directory corresponding to the selected variant. You should only use variants coming from the current project space, to avoid problems when exchanging your projects.
5.: The name of the selected variant, coming from the directory name.
6.: The extension of the body files produced by the target.
7.: The description of the selected variant.
Note 1: See the “Active Code Template” section for more info about creating new variants.