CMake Editors Support

CMake Editor Modes

There are CMake syntax highlighting and indentation supports for several editors:

• Emacs combined syntax highlighting and indentation mode. To enable it, add the following to your .emacs file:

; Add cmake listfile names to the mode list.
(setq auto-mode-alist
	  (append
	   '(("CMakeLists\\.txt\\'" . cmake-mode))
	   '(("\\.cmake\\'" . cmake-mode))
	   auto-mode-alist))

(autoload 'cmake-mode "~/CMake/Docs/cmake-mode.el" t)

• VIM syntax highlighting and indentation mode. To enable indentation, copy indentation file to your .vim/indent directory, syntax highlighting file to your .vim/syntax directory and add the following to your .vimrc:

:autocmd BufRead,BufNewFile *.cmake,CMakeLists.txt,*.cmake.in runtime! indent/cmake.vim 
:autocmd BufRead,BufNewFile *.cmake,CMakeLists.txt,*.cmake.in setf cmake
:autocmd BufRead,BufNewFile *.ctest,*.ctest.in setf cmake

• Eclipse CMake Editor. Plug-in for the Eclipse IDE providing syntax coloring and content assist for editing CMakeLists.txt and any file ending in a .cmake extension. Integrates the CMake command reference documentation into the Eclipse Help system.

• Kate, KWrite, KDevelop and all other KDE applications, which use the kate text-editing component support cmake syntax highlighting. Currently you have to open the settings dialog and choose download (Settings -> Configure Kate -> Editor -> Highlighting -> Download) and there select CMake in the listbox. Then the cmake syntax highlighting definition file for kate will be downloaded and installed. From KDE 3.4 and later cmake syntax highlighting will come with standard KDE.

• UltraEdit (an approach) save the jpg as text: File:Wordfile.jpg

• Enscript syntax highlighting rules. To enable it:
  1. copy cmake.st in the hl/ directory.
  2. add the following in the namerules section of the hl/enscript.st file:

  /CMakeLists\.txt/               cmake;
  /\.cmake.*$/                    cmake;
  /\.ctest.*$/                    cmake;

• SciTE version 1.73 has CMake support. To enable the feature edit SciTEGlobal.Properties and remove the comment before cmake lines.

• TextMate is a wonderful text editor for OS X. CMake Bundle. This plugin adds syntax highlighting for Cmake files.

• NEdit support was added by Philippe Poilbarbe

Creating New Editor Mode

The best way to start is to check the logic in existing ones. Make sure to enable indentation for files that match the following file names:

• CMakeLists.txt
• *.cmake
• *.cmake.in
• *.ctest
• *.ctest.in

Eclipse + CDT Version Information

CDT 3.1.2 goes with Eclipse 3.2 --> These are the stable versions as of May 2007.
CDT 4.0 is a Major step forward and needs Eclipse 3.3 to run. Both of these projects are in Beta release as of May 2007. The final releases are supposed to be around mid June 2007.
As of June 4 2007, if you want to try the latest versions then Eclipse 3.3RC2 and CDT 4.0 RC2 are the matched pair that you will need.

Getting Eclipse updated with CDT is fairly easy if you download the tar.gz files for both Eclipse and CDT. Untar the Eclipse distribution. This will create a directory called "eclipse". Now untar CDT distribution so that the output from CDT merges with the "eclipse" directory. This is easiest done if both the eclipse distribution and the cdt distribution files are in the same directory. Then merely run tar -xvzf on both tar.gz files.

Basic Tutorial

Eclipse CDT supports projects that already provide a makefile so this is good news for CMake users.

The basic steps to get Eclipse + CDT + CMake working are:

  1) Use CMake to generate makefiles for your project
  2) Create a new project in Eclipse using the top level directory of your project as the "Project Directory". The type of project to create should be a "Makefile C++"
  3) Create an "External Tool" to run cmake from within Eclipse

Eclipse CDT can interoperate with CMake by creating a "Standard Makefile" project, running CMake, and then having CDT to run make on the generated makefiles. Eclipse CDT works better if the build files are somewhere in project directory such as a subdirectory (for example Build).

A typical workflow would be something like this.

In a terminal program "cd" into the top level of your project directory ideally where your CMakeLists.txt file resides. Create a directory called "Build". cd into Build and then run ccmake/cmake using the parent directory as the target for cmake. So, for example if we have a project called "MyGreatProject" located in /Users/mike/Projects, then the terminal commands would look like the following:

[mjackson@Thor:]$ cd /Users/mike/Projects/MyGreatProject
[mjackson@Thor:]$ mkdir Build
[mjackson@Thor:]$ cd Build
[mjackson@Thor:]$ ccmake ../

At this point we have bootstrapped the process somewhat so Eclipse throws less errors when we setup the Eclipse Projects.

Launch Eclipse. Select /Users/mike/Projects as the "Workspace" (using the example from above). Go to "File->New Project" Select C++ Standard Makefile Project Go through the wizard making the appropriate selections and entries. At some point during this wizard there will be a tab that allows you to over ride the standard "make" command invocation. The tab may have a title such as "Make Builder". Uncheck "Use default" and enter the following into the "Build Command" text field.

"make -C ${project_loc}/Build" ( Without the quotes). For multi-core systems and if you want to use multiple compile jobs, then use:

make -j2 -C ${project_loc}/Build (where '2' is the number of jobs to use.Adjust for your own system)

There will also be another tab called "Binary Parsers". Select that tab and be sure that the appropriate binary type is selected for your system. Continue on with the wizard until finished.

Your new project should now be ready. Select the project in the C/C++ Projects view then select the "Project->Build Project" Menu to build your project.

Now, technically you _could_ use a completely out of source build and this will work with eclipse, but eclipse will be unable to find your binaries when finished, which makes the setup of debugging and running your app from Eclipse a bit more tricky.

Creating an External Tool to run cmake

If you edit your CMakeLists.txt file, then you will need to go back out to your terminal and rerun cmake. OR you can create an external program launch configuration and run cmake from within eclipse. To do this select the "Run->External Tools->Show External Tools Dialog..." menu. Create a new "Program" and call it Cmake. in the "Location" text field, type the absolute path to cmake (/usr/local/bin/cmake). If the "Working Directory" area insert the following: "${project_loc}/Build" and in the Arguments section insert the following: "../". In the "Refresh Tab" Select ""The project containing the selected resources". In the "Common" tab check the "External Tools" selection. This will put a shortcut in the "Run" menu for you. Click the Apply Button and then run. cmake will now run on your project directory.

Parsing Errors more efficiently

The CDT Error Parser cannot handle error messages that span more than one line, which is the default gcc behavior. In order to force gcc to generate single line error messages with no line wrapping, add to your CMakeLists.txt:

IF(CMAKE_COMPILER_IS_GNUCC)
  SET(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -fmessage-length=0")
ENDIF(CMAKE_COMPILER_IS_GNUCC)
IF(CMAKE_COMPILER_IS_GNUCXX)
  SET(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fmessage-length=0")
ENDIF(CMAKE_COMPILER_IS_GNUCXX)

Automatic Discovery of Include directories and other compiler items

In order for the CDT discovery mechanism to catch the compiler options and definitions automatically from the build output, enable the "Enable build output info discovery" in the project properties and set the CMAKE_VERBOSE_MAKEFILE variable in your CMakeLists.txt.

SET(CMAKE_VERBOSE_MAKEFILE ON)

If you don't want to hard-code this behavior in CMakeLists.txt, you can achieve the same effect by telling CDT to invoke make as

make VERBOSE=1

---

CMake: [Welcome | Site Map]