Building with CMake

From Sim-Im
Jump to navigation Jump to search

Building for Linux


Note: If you use binary packages for these dependencies you will need the header packages (normally named package-dev or package-devel) of these packages, too. You might also need header packages of dependencies of these, for example:

  • libpng (Dependency of QT3)
  • libmng (Dependency of QT3)
  • Maybe others

Optional Packages:

  • OpenSSL (For using encrypted connections, some plugins need this.)
  • ASpell (If you want spell checking and are not using KDE.)
  • kdelibs (For KDE integration.)
  • GnuPG (Not required at build time; required if you want to use GPG encryption for messages.)


First create a build dir

mkdir -p sim/source sim/build

Put the source code in the source dir, cd to the build dir and run:

cmake ../source

That will run cmake's configure checks which will check if you have got every programs/libraries/headers,that are needed to compile sim. If you want to tune some of the variables, you can either use the interactive mode of cmake

cmake -i ../source

or you can use cmake's nice gui:

ccmake ../source

If that is done just run


in the build dir to build sim. When it finished, run

make install

to install sim.

Building for Windows



Once you've installed all requried packages, make sure you've set the following environment variables are correct:

  • QTDIR - the path to your Qt3 installation
  • CMAKE_INCLUDE_PATH - paths to the headers of all installed packages
  • CMAKE_LIBRARY_PATH - paths to the libraries of all installed packages

For example:

QTDIR=[TODO: write an example value here]

If some values are missing, use should set them using set command:

 C:\>set QTDIR=[TODO: write an example value here]


After you've checked out the sources, create a new directory 'sim-im-build'. Now you can call cmake (or cmakesetup on win32) by switching into 'sim-im-build':

cmake ..\sim-im 

When cmake is ready and all required packages were found you can start compiling sim with 'make' (or mingw32-make or nmake)

See Also

Building with Cmake FAQ