Starting with version 2.6.0 CMake supports generating projects for CDT
4.0 or newer. Here you can find
information how to use this.
If you are using an older version of CDT or CMake without the Eclipse
generator, you can configure Eclipse also manually to work with CMake
based projects. This is described
Here you find information about
plugins which offer syntax highlighting and more for CMake in Eclipse.
(cmake . -G KDevelop3)
The KDevelop project generator is available in CMake since version
2.2.0. It works with KDevelop 3.1.1 and newer. Out-of-source builds are
fully supported. As with all other project generators, adding files to
the project has to be done by editing the CMakeLists.txt.
Beside creating all the same files as UNIX Makefile generator, it
creates in the toplevel binary directory files:
The first one is XML describing the project, while the second one is a
list of relative paths to the source files. The source files are grouped
based on globbing expression in the XML file.
(cmake . -G "CodeBlocks - Unix Makefiles")
Starting with version 2.6.0 CMake also comes with a project file
generator for the CodeBlocks IDE. This
support is still in beta and needs feedback in order to mature.
"Build file" doesn't work
Sometimes cancelling the build doesn't work
The following targets are available:
rebuild_cache : just runs the cmake configure and generate steps,
but don't actually start building
edit_cache : run the user interface for working with
cmake/modifying the cache contents. This is either cmake-gui or
The following variants of the generator are available:
"Unix Makefiles" : This generator generates Makefiles for make under
Unix and also for cygwin (i.e. with Unix paths)
"MinGW Makefiles" : Windows only, generates Makefiles for GNU make
from the MinGW project, the makefiles work
also with other "native" GNU make versions for Windows. You can get
this e.g. from http://unxutils.sourceforge.net, the download
. From that zip file only /usr/wbin/make.exe is needed. The GNU make
from www.steve.org.uk is version 3.75, this version has a bug, it
does not work. The generated Makefiles use DOS/Windows paths and use
cmd.exe as shell. GNU make supports parallel builds and can also be
used with cl.exe as compiler. This can be done by setting the
environment variables CC and CXX to cl.exe before running CMake.
"MSYS Makefiles" : Windows only, generates Makefiles to be used
under MSYS. It uses Unix-like
paths and sh.exe from MSYS as shell.
"NMake Makefiles": Windows only, generates Makefiles for MS nmake.
The makefiles use DOS/Windows paths and care for nmake specific
issues. The environment has to be setup correctly, e.g. by running
vcvars32.bat. This can be done by running from the "Visual Studio
"NMake Makefiles JOM" : Like "NMake Makefiles", but generates
Makefiles for jom instead of nmake. jom is like nmake, but supports
the -j flag. jom.zip should point to the newest release. Get jom
through ftp - 0.9.4 has been confirmed
to work. Make sure the containing folder is in the PATH.
"Borland Makefiles": Windows only, generates Makefiles for Borland
make. The makefiles use DOS/Windows paths and care for Borland make
"Watcom WMake": Windows only, generates Makefiles for Borland make.
The makefiles use DOS/Windows paths and care for Watcom wmake
How to generate NMake Makefiles using Visual C++ Express Edition (free Visual Studio 8)
To compile your project on the command line using the one-year free
Visual C++ 2005 Express Edition, you can generate NMake Makefiles with
CMake, and then use nmake.
To use the free compiler, 'Visual C++ Express Edition' and 'Microsoft
Platform Software development Kit (SDK)' have to be downloaded and
installed separately. The batch file for the 'Visual Studio 2005 Command
Prompt' must be update to include the path, the include directory, and
the libraries for Microsoft Platform SDK.
Download VC Express *and* Platform SDK from
http://www.microsoft.com. Install them in C:\Program Files. The
license expires one year after your start using it.
Create a batch file called 'VS8_Command_Prompt.bat' in your home
directory (for example in C:\cygwin\home\my_username\Bin). Edit
this file and type:
<nowiki> @echo off if not exist "C:\Program Files\Microsoft Visual Studio 8\VC\vcvarsall.bat" goto missing echo call "C:\Program Files\Microsoft Visual Studio 8\VC\vcvarsall.bat" call "C:\Program Files\Microsoft Visual Studio 8\VC\vcvarsall.bat" @set PATH=C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Bin;%PATH% @set INCLUDE=C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include;%INCLUDE% @set LIB=C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Lib;%LIB% goto :eof :missing echo Missing file echo "C:\Program Files\Microsoft Visual Studio 8\VC\vcvarsall.bat" goto :eof</nowiki>
Create a Windows shortcut called "VS8_Command_Prompt" in your Desktop.
Right click and go to Properties. Edit the shortcut tab (replace x86
with amd64, x64, ia64, x86_amd64, or x86_ia64 depending on your