X.A.2 Building from sources

All the sources are delivered in an archive containing an SRC directory and several levels of sub-directories. The sources of the program are delivered with different Makefiles and BASH or BAT scripts that can be used for the compilation of the different targets:

• The makefiles must be used with the GNU “make” command. This means that on Windows OS, you should install the corresponding binaries. “MSYS” is used for several UNIX commands, and have tested different versions of the GNU C/C++ compilers downloaded with different versions of “MINGW”. The compilation has also been tested with different versions of Microsoft Visual C++ compiler.

• The “BASH” and “BAT” scripts are located in the “SRC” main directory. “BAT” scripts are used for the compilation on Windows OS, and “BASH” scripts on LINUX. These scripts define part of the compilation environment, and you may have to modify them if you want to recompile the sources.

• The main Makefiles are located in “SRC/MAKEFILES” directory. They include sub-makefiles located in the “SRC/MAKEFILES” directory and in the sources sub-directories. The Makefiles in “SRC/MAKEFILES” directory also define part of the compilation environment and will have to be adapted in order to re-compile the sources. These adaptations consist mainly in modifying paths to match installation on your computer. (Ruby installation directory, for example.)

• The makefiles in source directories are built automatically. You just have to ask for the building of “dependences” target. For example,you type the command “build_mingw32.bat dependences”. (You do not need to do this if you do not modify the sources.)

• The association of script commands, makefiles and targets is summarized in Table X.A.1. Besides, several targets are also defined that do not depend on the platform:

  • “clean” cleans all the objects, libraries and other files produced by the compiler command.

  • “dependences” produces or updates the makefiles in the source directories.

  • “ruby” to build all the ruby extensions available in the Makefile.

  • “python” to build all the python extensions available in the Makefile.

  • “com” to build the COM component.

  • “archives” creates a 7Zip archive of the “OUTPUTS” directory.

  • “outputs” produces all the libraries in other outputs in “OUTPUTS” directory, and then builds the “archive”

• Some targets are specific to the .NET assembly compilation:

  • “signkey” for the update of the assembly signature.

  • “install” to install the assembly in the Global Assembly Cache (GAC).

• On Windows OS, the compilation of python extension is possible with the MSVC compilers (“build_python_msvc32.bat” and “build_python_msvc64.bat” scripts) or with GNU compiler (“build_mingw32.bat” and “build_mingw64.bat” scripts). It is advisable to use the GNU compilers as it allows to build all the 32-bits python extensions with a single version of the compiler.

Examples of builds follow:

        build_linux32.bash ruby
        build_linux32.bash ruby_23
        build_linux32.bash outputs
        build_mingw64.bat com
        build_mingw64.bat ruby
        build_mingw64.bat outputs
        build_python_27.bat
        buildbuild_python_win32
        buildbuild_python_win64
        ...

Note: for 32-bit version 2.4.* of ruby, the “include/ruby/ruby.h” has been slightly modified: “DEPRECATE_BY” lines 1381 and 1390 have been commented. Otherwise, the compilation resulted in error messages. This has been done on Windows and on Linux.