Commandline arguments

Version

• -v print         print simulator version
• --version

Help

• -h print         print help message
• --help

Put all generated code in a namespace

• -n "namespacename"
• --namespace "namespacename"

Put all generated code in a single header

• -s "singleheaderfilename"
• --single-header "singleheaderfilename"

Generate structures

• -g
• --generate-structures

Change to class names

• -c
• --change-to-class-names

Generate input stream

• -i "inputstreanclassname"             Input Stream Class Name
• --generate-input-streams "inputstreanclassname"

Generate output stream

• -o "outputstraeamclassname"          Output Stream Class Name
• --generate-input-streams "outputstraeamclassname"

Output directory

• -d "generatedfilesdirectory"             Output Directory Name
• --output-directory "generatedfilesdirectory"

First undefined attribute

• -u "firstsymbolxx"             Undefined Attribute Name
• --undefined-attribute "firstsymbolxx"

The Blender Class Generator tool is located in the src/tools/blenderclassgenerator directory. The tool is designed to read the dna.c file generated in a blender build. The file is generated by makesdna during a build of  Blender. The blenderclassgenerator produces C++ structures and generates stream members for those structures to read a blender 3d file. The generated header file (src/include/dna.h.in) is used by the MSTS2Blender utility to read and write Blender 3d editor files (*.blend). A default dna.h.in is supplied in the src/include directory and maintained and updated in the svn repository. The program is made up of a reader and main program files.).

The error and line number is written to cerr.

• 1 = dna.c is corrupt
• 2 = unknown exception
• 3 = cannot read a fixed sized array

Initial Branch

To establish an initial branch – download or export from the vendors svn, a copy of the current vendor source, renaming the directory to something suitable (ogre, wxwidgets etc.). From the OSRail repository import the newly named directory into the top directory of the repository under vendor. OSRail does not use tags for vendor branches so note the revision in the import comment for example (CMake maintenance branch branch 2.8.0 - last change Nov 11, 2009 svn-1347) it will be required to identify the revision for a merge of a newer revision to the trunk line of CMake.

Update a Branch

To update a vendor branch - download or export from the vendors svn, a copy of the updated vendor source, use the vendor branch name (cmake-2.8.0). Checkout the vendor directory under the vendor directory in the top of the OSRail repository (http://wush.net/svn/sehenley/vendor/cmake). Use the operating system to copy or move the exported vendor source to the checked out vendor source. Check for files and directories that have been removed and use svn to remove them from the working copy. Comment the working copy to the repository.

--- Or

Checkout the new cmake branch/tag to the working directory cmake-2.8.0 (http://www.cmake.org/files)

Run the Perl script svn_load_dirs.pl. In the working directory (not free, no copyright, not available from Debian site, but available from http://subversion.tigris.org)

./svn_load_dirs.pl http://wush.net/svn/sehenley/vendor cmake cmake-2.8.0

Update the Trunk

To update the trunk vendor branch – checkout the trunk vendor branch (http://wush.net/svn/sehenley/trunk/vendor/cmake). From the repository merge the previous vendor branch in the top directory with the current vendor branch into the checked out version of the trunk vendor branch. For example http://wush.net/svn/sehenley/vendor/cmake (svn revision 1324 ) is merged with http://wush.net/svn/sehenley/vendor/cmake (svn revision (head) ) into working directory c:/working/cmake. Resolve any conflicts etc. and commit the result back to the trunk. Use this copy to make any program changes required and commit them to the trunk branch after testing.

Caution: The Windows build of CMake, modifies the cmake source - do not commit these changes.
Self Modified Sources are:

• Tests/.NoDartCoverage
• Utilities/cmexpat/.NoDartCoverage
• Utilities/cmexpat/cm_expat_mangle.h
• Utilities/cmexpat/expat.h
• Utilities/cmzlib/.NoDartCoverage

If the header files are commited - they will prevent a Linux build.
Caution: You should remove the cmake directory when finished or you will get an error running script svn_load_dirs.pl on the next update.