Build Instructions

From Commontk
Jump to: navigation, search
Home < Build Instructions

The following instructions are valid as of October 2012 (if something is incorrect, please report an issue).



Anonymous checkout Anonymous checkout behind a firewall CTK developer with write access
git clone git://
git clone
git clone

Build with CMake

mkdir CTK-superbuild
cd CTK-superbuild
ccmake ../CTK

CMake Configuration

  • set QT_QMAKE_EXECUTABLE for 4.6 development install if needed (use {path/to/qt}/bin/qmake not {path/to/qt}/qmake/qmake)
  • turn on the parts of CTK you want to build

How to use CTK ?

See the Examples project that illustrates how CTK can be integrated into applications.


Simple Git

These are shortcuts for people used to the 'cvs or svn style' of source code management:


  • checkout
git clone

(or use anonymous option listed above)


git pull --rebase


  • commit (commit is to local version, push sends it to upstream server)
git add <changed files>
git commit -m <message>
git push

Intermediate Git

  • check update before merging (look at diff):
git fetch
git diff origin master
git rebase
  • Making a repository hosted on github that can track [1]
  • If you have changes pending that you aren't ready to commit, you can't rebase on top of them unless you do this:
git stash
git pull --rebase
git stash pop
  • to get the code from a branch
git clone <repository> <dir>
cd <dir>
git checkout origin/<branchname>


List of needed tools and libraries used when building CTK:

  • Git: To download source code
  • Qt: Dependency needed. You need to compile it in your machine before building CTK
  • CMake: Cross-platform build system
  • Patch for Windows: Needed to apply patches to external thirdparty libraries source code
  • SVN: To update some third-party libraries automatically like PythonQt
  • CVS: To update some third-party libraries automatically like KWStyle


  • Python: If you plan to use Scripting
  • DoxyGen: To generate documentation from source code on your machine
  • GraphViz: To generate documentation from source code on your machine