ChasmCodeGeneration

For an introduction on generating code and compiling your first Chasm project, see the introduction.

To read about the philosophy behind the code generation, see here.

To read about how to implement in Chasm, read here.

To see the layout of a generated file, read here.

To understand the defines in the generated code, see ChasmDefines.

This describes the binaries to generate your source files.

See here for help with Makefiles.

The structure of a Concept is in Chasm so this generates source files to place your implementation into. The source files have many different defines which are overwritten by chasmprocess to create the actually compiled files.

To create a file:

• create a .chasmxml file using the chasmgui
• type 'chasm2C concept'. This generates .[Ch] files from the .chasmxml file.

To Implement:

• Modify the .[Ch], CONCEPTBuilderPOSTFIX.[Ch] files.
• Modify the .chasmxml file with ChasmGui.
• see tips on where to place your implementation.

To Compile:

• use chasmprocess to turn the .C, .h and .chasmxml files into .chasm.h and .chasm.C files.
• compile the .chasm.[hC] and CONCEPTBuilderPOSTFIX.[Ch] files with your normal compiler.

NOTE: Please add instructions for a build process in XCode and Eclipse!

NOTE: See here for help with Makefiles.

To Create a Supplemental code file:

• When running the chasm2C command, add the -s parameter to chasm2C. This will then generate a concept_sup.h file as well as adding extra code to the concept.[Ch] files.
• If the compiler is having trouble finding the supplemental header, make sure you specify it as a local or global header by throwing in the -l option for global headers or the -L option for local headers.

To create a ChasmBuilder of a given POSTFIX (ex. SVE is a POSTFIX):

• type 'chasm2C -b -p POSTFIX concept'. This will create a file conceptBuilderPOSTFIX.h and conceptBuilderPOSTFIX.C which holds an object which inherites off of the object conceptBuilder.

See ChasmCodePhilosophy.