To make it easier to build the Ivf++ libraries a new build system has been developed for the 1.0 release. This system automatically handles the download, building and installing dependancies as well as building the main Ivf++ libraries.
The new Ivf++ build system is based on CMake and Python. The build system has been tested with Python 2.3/2.4 and CMake 2.4. If the documentation is to be build as well Doxygen is required.
The first step in building Ivf++ is to make sure all dependencies are available and installed at a location that can be found by the Ivf++ build system. The Ivf++ build system can automatically download, build and install the needed dependencies. Please note that FTGL requires Doxygen to build and install correctly. To do a complete build of the Ivf++ dependencies to following procedure can be used:
$ ./ivfbuild depends download ... All needed packages are downloaded ... and patched, please see the patches dir $ ./ivfbuild depends build /usr/local ... All packages are built with the install ... prefix /usr/local ...
If a prefix is used located at directory writable to root only execute the following commands as root:
# ./ivfbuild depends install /usr/local ... Packages are installed ...
The main build of Ivf++ is configured using the "./ivfbuild configure" subcommand. This command takes the build type as a required parameter. The selectable build types can be:
To configure a shared_release build installed with the /usr/local prefix, issue the following command:
$ ./ivfbuild configure shared_release /usr/local ... The CMake build system is configured ...
Ivf++ is not build within the source tree. Under Linux the build is located in the linux2_build folder. In this folder CMake will generate the "real" Makefiles.
To start the build issue the following command:
$ ./ivfbuild build ... The Ivf++ libraries are built ...
The Ivf++ libraries are installed as root using the following command:
# ./ivfbuild install
This document describes how to build the Windows version of the Ivf++ library from the source tree. A more convenient way of using the library is to use the pre-compiled packages available at sourceforge, which contain binary versions of the Ivf++ library and dependencies.
To make it easier to build the Ivf++ libraries a new build system has been developed for the 1.0 release. This system automatically handles the download, building and installing dependancies as well as building the main Ivf++ libraries.
The new Ivf++ build system is based on CMake and Python. The build system has been tested with Python 2.3/2.4 and CMake 2.4. If the documentation is to be build as well Doxygen is required.
The first step in building Ivf++ is to make sure all dependencies are available and installed at a location that can be found by the Ivf++ build system. The easiest way of doing this is to download the ivf-win32-depend package from sourceforge and install it. This package contains pre-built version of the libraries required for Ivf++. If this package is not used the following packages has to be build first:
Please make sure that they are available for the build environment used. If Visual Studio is used they are set in the Tools/Options/Projects/VC++ Directories. If a command line build is used please set the INCLUDE and LIB environment variables.
The main build of Ivf++ is configured using the ./ivfbuild configure subcommand. This command takes the build type as a required parameter. The selectable build types can be:
To configure a shared_release build issue the following command:
C:\..\> ivfbuild configure shared_release ... The Ivf++ build is configured ...
If a command line build is desired use the following command instead:
C:\..\> ivfbuild configure shared_release nmake ... The Ivf++ build is configured for command line build ...
Ivf++ is not build within the source tree. Under Linux the build is located in the linux_build folder. In this folder CMake will generate the "real" Makefiles.
To start the build issue the following command:
C:\..\> ./ivfbuild build ... The Ivf++ libraries are built ...
All executables built by the library are installed in the bin-directory in distribution-directory. Libraries are build in the lib-directory of the distribution-directory.