|Top Previous Next|
Code generation > Code frames > jamfile
When the c++ code is generated, in addition a file with the name jamfile.txt is generated, which helps to create a "jamfile" for the use with with the boost build system.
Followingly, an example of such a file is represented, which was produced for a project with the start rule translation_unit and which uses dnode's.
# frame for a bjam jamfile
lib regex : : <name>[name of the regex lib] <search>[search path for the regex lib] ;
lib filesystem : : <name>[name of the filesystem lib] <search>[search path for the filesystem lib] ;
lib xerces : : <name>[name of the xerces lib] <search>[search path for the xerces lib] ;
tt_boost_config tt_exception tt_lib tt_msg tt_node tt_domnode tt_xerces
exe translation_unit : [path of the TextTransformer code]/$(CPP_SOURCES).cpp [ glob *.cpp ] filesystem regex xerces
: <include>[path to the boost directoy] // e.g. C:/Program Files (x86)/boost/boost_1_38
<include>[path to the TextTransformer code] // e.g. C:/Program Files (x86)/TextTransformer/Code
<include>[path to the xerces source] // e.g. C:/Program Files (x86)/xerces-c-3.0.1/src
If CTT_ParseStateDomPlugin is not set as plugin-type the lines concerning xerces don't appear in jamfile.txt. The boost filesystem library isn't always required either. However, this isn't automatically checked.
This page belongs to the TextTransformer Documentation
|Home Content German|