Difference between revisions of "CMake"

From KitwarePublic
Jump to navigationJump to search
m (→‎autoconf: added note to use CVS when looking at this code)
(→‎Basic Introductions: This is where I put the CMake/Language Syntax link.)
Line 32: Line 32:
* [http://www.linuxjournal.com/article/6700 Cross-Platform Software Development Using CMake]
* [http://www.linuxjournal.com/article/6700 Cross-Platform Software Development Using CMake]
* [http://clubjuggler.livejournal.com/138364.html CMake: The Cross Platform Build System]
* [http://clubjuggler.livejournal.com/138364.html CMake: The Cross Platform Build System]
* [http://kernigh.pbwiki.com/CMake Introduction to the CMake language]
* Syntax of the CMake language
** [http://www.cmake.org/HTML/syntax.html A quick introduction to CMake syntax]
** [[/Language Syntax]] (wiki page)
====Specific Topics====
====Specific Topics====

Revision as of 13:32, 14 March 2008


Welcome to CMake, the cross-platform, open-source make system. CMake is used to control the software compilation process using simple platform and compiler independent configuration files. CMake generates native makefiles and workspaces that can be used in the compiler environment of your choice. CMake is quite sophisticated: it is possible to support complex environments requiring system configuration, pre-processor generation, code generation, and template instantiation.

You will find here not only documentation for CMake, but also for CPack and CTest.


Primary Resources - Look here first!

Development Topics


Basic Introductions

Specific Topics

  • Qt with CMake
    Explains how to use CMake to build software with Qt4, Qt3 and KDE3.

Converters from other buildsystems to CMake

All converters listed here are not "complete", i.e. the generated CMake files are not 100% finished, in all cases some work is left for the developer.


  • am2cmake (requires Ruby) Converts automake/autotools/libtool based projects to CMake, specialized in converting from KDE 3 to KDE 4, should also work for others. This one has been used for converting the KDE buildsystem to CMake.

When converting from autoconf, the generation of "config.h" files can be complex. You may wish to examine the CMake scripts within the gcc-xml project at gcc-xml (XML output of gcc's internal representation). The project builds a modified gcc compiler using CMake. This is an impressive feat of autoconf conversion.

For example, the HAVE_THIS/HAVE_THAT defines used within autoconf projects can be overwhelming when converting a large project. Below is a snippet from the "config.h.in" file within gcc-xml:

/* Define to 1 if you have the `bcopy' function. */
#cmakedefine HAVE_BCOPY @HAVE_BCOPY@
/* Define to 1 if you have the `bsearch' function. */
/* Define to 1 if you have the `bzero' function. */
#cmakedefine HAVE_BZERO @HAVE_BZERO@

While not a drop-in tool, their scripts are an excellent starting point. Be sure to reference the code from their CVS repository instead of the out-of-date tarball listed.



Visual Studio

Success Stories

More Topics



  • Testing With CTest
    Introduces to testing with CTest, submitting dashboards, and using CMake to add tests to the test system.
  • CTest Scripting
    Describes the scripting with CTest which can significantly simplify and automate testing and submitting dashboards.

More Information



More Information


CMake: [Welcome | Site Map]