Installing the 1.14 release

Configuration

The most common build system used for VXL is CMake. You should first download and install CMake. VXL requires CMake version 2.6.3 or higher.

Extract the VXL source into the directory vxl-1.14. Create a separate output directory bin parallel to the source directory:

   .../.../... ---+--- vxl-1.14 ---+--- vxl
                  |                     |
                  |                     +--- vcl
                  |                     ...
                  |
                  +--- bin

Let us call the former $VXLSRC and the latter $VXLBIN.

Change current directory to $VXLBIN and run CMake, specifying $VXLSRC as the source directory.

Unix and Cygwin:

Run the Curses based front-end

      ccmake $VXLSRC
    

or the command line front-end

      cmake -i $VXLSRC
    

Windows:

Run CMakeSetup and specify the source and binary directories as $VXLSRC and $VXLBIN, respectively. In the box on the upper right, choose the build system you use.

Repeatedly select "Configure" ("C" on Unix) until the entries stop changing and you get the chance to generate the makefiles ("OK" on Windows, and "G" on Unix).
You may ignore any "something-NOTFOUND" message since these refer to optional components. But if you are sure that one of these components is present on your system, manually fill in the correct path and re-run configure.

In the CMake interface, you can choose which parts of the VXL tree to build. The default is to build everything except vgui and its dependents. Building vgui requires the presence of OpenGL and GLU. Often, these are in a platform specific area of the machine, and hence cannot be detected by CMake. If you have these on your system, and wish to build vgui, set BUILD_VGUI to "ON" and make sure the appropriate entries in the CMake cache are valid. With Windows, the required libraries (MFC and OpenGL) are shipped with the operating system, so you should be able to build vgui without any issues.

Build

Now you can build the libraries.

Unix or Cygwin:

Run make

      make
    

Windows and MSVC:

Build VXL by loading the $VXLBIN\vxl.dsw into Developer Studio and building the ALL_BUILD target. This project is a little larger than Developer Studio can sometimes cope with, so you can do a full build from the command line:

      vcvars32.bat
      msdev vxl.dsw /MAKE "ALL_BUILD - Win32 Debug"
    

Or the speedier release version

      msdev vxl.dsw /MAKE "ALL_BUILD - Win32 Release"
    

Windows and Visual Studio 7 and above:

Build VXL by loading the $VXLBIN\vxl.sln into Developer Studio and building the ALL_BUILD target.

Test

You can run the test suite using the ctest program that came with CMake

Documentation

Problems and where to get help

Have a look through the Build FAQ.

If you think you have found a bug, or if you have an installation or build problem, please submit a bug report on the vxl-users mailing list. Also supply the following information unless you know for certain it is not relevant:

• Exactly what you did and exactly what goes wrong. Be verbose. We need to know this in order to help. If you have problems configuring VXL, include the options you gave to configure and the output it produced. If you have problems compiling VXL, include the command the makefiles issued, as well as the entire error message.
• Compiler and compiler version number. For gcc, this means we want the output of the two shell commands "gcc -v" and "g++ -v" (yes, both, please - they have been known to differ). For other compilers try -V, -ver, --version or read the manual.
• Operating system (e.g. linux/solaris/irix) and architecture (e.g. i386/sparc/mips).

vxl-maintainers at lists dot sourceforge dot net
Hosted by