Introduction

Libwm is built using a CMake-based system. CMake configures and generates project files or Makefiles for your favorite compiler system. Libwm has been built with various versions of GCC and GNU Make, Microsoft Visual C++ Express Edition 2008 and Apple Xcode.

Requirements

CMake version 2.6
Mercurial for checking out the source code
Boost libraries version 1.35 or newer

Libwm uses only Boost headers, but the example applications use thread and date_time libraries
Windows users can use pre-built binaries from http://www.boost-consulting.com/

Unix requirements:

dlopen(3)
Xlib
OpenGL development files

Doxygen for generating api docs OPTIONAL

Graphviz for generating diagrams in API docs OPTIONAL
TeX Live for generating LaTeX and .pdf API docs OPTIONAL

sudo apt-get install cmake libboost1.35-dev libc6-dev libx11-dev
sudo apt-get install mesa-common-dev  # or nvidia-glx-XXX-dev for OpenGL dev files
sudo apt-get install doxygen graphviz texlive # if you want to build the API docs with diagrams and .pdf's

Getting the source code

The latest development source code can be cloned from the Mercurial repositories.

hg clone https://libwm.googlecode.com/hg/ libwm

Configuring the build

CMake is used to configure the build system and generate the actual build files (Makefiles, Visual Studio project files, etc). You can use the command line cmake or the cmake-gui if you prefer GUI's.

mkdir libwm/build
cd libwm/build
ccmake ..

If the default FindBoost.cmake is unable to locate your Boost installation, you can specify the location of your boost installation using a command line parameter ("-DBOOST_ROOT=C:\Program Files\boost_1.37.0\"), by using the Add Entry-button in the GUI to define the BOOST_ROOT variable or by using the CMAKE_PREFIX_PATH environment variable.

Build the library

After generating the build system you can build using the Makefiles or project files generated by CMake. Below is an example using make. Alternatively, you can open the generated project files in your IDE.

make
make doc
make pdf
make package
make package_source

Comment by sschuberth, Aug 22, 2009

Minor typo, I believe it should be "cmake" instead of "ccmake" under "Configuring the build".

Comment by maililistaalterego, Aug 25, 2009

Nope, it's not a typo. I put ccmake (the console/curses gui) instead of the command line cmake intentionally there so users would find the compile time configuration options easier. You could also use cmake-gui.