|(19 intermediate revisions by 10 users not shown)|
==CMake Editor Modes==
There are [[CMake]] syntax highlighting and indentation supports for many editors:
This has [://.kitware.com/cmake////].
* '''[http://www.eclipse.org/cdt/ Eclipse]''' There are two plugins for Eclipse:
** The [http://cmakeed.sourceforge.net CMakeEd] plugin for Eclipse provides syntax coloring and content assist for editing CMakeLists.txt and any file ending in a .cmake extension. It also integrates the CMake command reference documentation into the Eclipse Help system. This plugin does NOT do project management for you or generate CMake files for you. You are still responsible for this part. CMakeEd just makes writing the CMakeLists.txt files easier.
** The [http://www.cmakebuilder.com/ CMakeBuilder] plugin provides a user friendly interface to easily manage CMake-based projects, with the following features: advanced parser, Advanced CMake outline, CMakeBuilder perspective, symbol table and environment inspector, CMake files editor with syntax highlighting, code assist, wizard-oriented project management, Project Nature CMakeBuilder for CDT projects, and incremental project builders.
** '''[[Eclipse_CDT4_Generator|Here]]''' you find documentation how to use the Eclipse CDT project generator of CMake.
** '''[[CMake:Eclipse_UNIX_Tutorial|Here]]''' you find documentation how to use Eclipse with the regular Makefile generator of CMake (for versions < 2.6 of CMake).
* '''[http://www.kdevelop.org KDevelop 4]''' supports CMake-based projects natively.
* '''[http://qt.nokia.com/products/developer-tools/ QtCreator]''' supports CMake-based projects natively.
* '''[http://www.netbeans.org NetBeans]''' supports CMake-based projects [http://forums.netbeans.org/ntopic26390.html natively since version 6.8].
* '''Emacs''' [http://www.cmake.org/CMakeDocs/cmake-mode.el combined syntax highlighting and indentation mode]. The file in the repository used to not function properly when running fill-paragraph (M-q). There was a [[CMake Emacs mode patch for comment formatting|patched version]] to fix this, but it is largely unnecessary now that the one in the repository works properly now. To enable it, add the following to your ''.emacs'' file:
; Add cmake listfile names to the mode list.
'(("CMakeLists\\.txt\\'" . cmake-mode))
'(("\\.cmake\\'" . cmake-mode))
(autoload 'cmake-mode "~/CMake/Docs/cmake-mode.el" t)
I've been long irritated with having to deal with multiple buffers all name CMakeLists.txt. Emacs by default will call them CMakeLists.txt, CMakeLists.txt<2>, CMakeLists.txt<3>, etc.. This is really hard to switch back and forth when the buffer names are difficult to associate with location.
I've found a couple of solutions to this problem.
<ol><li>Use uniquify emacs package. This gives several options to automatically rename buffers based on their location on disk.
;; uniquify.el is a helper routine to help give buffer names a better unique name.
(when (load "uniquify" 'NOERROR)
(setq uniquify-buffer-name-style 'forward)
;(setq uniquify-buffer-name-style 'post-forward)
<li>Rename the buffer as part of the cmake-mode
(defun cmake-rename-buffer ()
"Renames a CMakeLists.txt buffer to cmake-<directory name>."
;(print (concat "buffer-filename = " (buffer-file-name)))
;(print (concat "buffer-name = " (buffer-name)))
(when (and (buffer-file-name) (string-match "CMakeLists.txt" (buffer-name)))
;(setq file-name (file-name-nondirectory (buffer-file-name)))
(setq parent-dir (file-name-nondirectory (directory-file-name (file-name-directory (buffer-file-name)))))
;(print (concat "parent-dir = " parent-dir))
(setq new-buffer-name (concat "cmake-" parent-dir))
;(print (concat "new-buffer-name= " new-buffer-name))
(rename-buffer new-buffer-name t)
(add-hook 'cmake-mode-hook (function cmake-rename-buffer))
I actually prefer renaming my buffers with my cmake-rename-buffer function, because the buffer names start with a lower case letter. :)
* '''Enscript''' [http://tristancarel.com/pub/patches/enscript/cmake.st syntax highlighting rules]. To enable it:
*# copy <tt>cmake.st</tt> in the <tt>hl/</tt> directory.
*#add the following in the <tt>namerules</tt> section of the <tt>hl/enscript.st</tt> file:
* '''[http://www.lugaru.com Epsilon]''' has a CMake [http://lugaru.com/ftp/for-v13/cmake.e extension] that supports syntax highlighting, indentation, and auto-completion of expressions for control statements such as if-else-endif, foreach-endforeach, and while-endwhile.
* '''[http://www.geany.org Geany]''' added CMake support in [http://www.geany.org/Main/20090215 version 0.16]
* '''[http://kate.kde.org Kate]''', '''KWrite''', '''[ http:// www.kdevelop.org KDevelop]''' and all other [http://www.kde.org KDE] applications, which use the kate text-editing component support cmake syntax highlighting since KDE 3.4.
* '''NEdit''' [http://www.cmake.org/Wiki/images/c/c6/NEditCMakeHighlighting-0001.tar.gz syntax highlighting support] was added by [http://public.kitware.com /pipermail/cmake/ 2007-May/ 014267.html Philippe Poilbarbe]
* '''[http:// notepad-plus.sourceforge.net/uk/site.htm Notepad++] ''' added CMake support in version 4.1
* '''[http://scintilla.sourceforge.net/SciTEDownload.html SciTE]''' version 1.73 has CMake support. To enable the feature edit SciTEGlobal.Properties and remove the comment before the CMake lines.
* '''[http://www.macromates.com TextMate]''' is a wonderful text editor for OS X. [http://www.bluequartz.net/binaries/CMake.tmbundle.zip CMake Bundle]. This plugin adds syntax highlighting for CMake files and rudimentary completion for command, properties and cmake variables.
* '''UltraEdit''' syntax highlighting [http://www.cmake.org/Wiki/images/5/56/UltraEditWordfile.tar.gz word file.]
* '''VIM''' [http://www.cmake.org/CMakeDocs/cmake-syntax.vim syntax highlighting] and [http://www.cmake.org/CMakeDocs/cmake-indent.vim 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
==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:
* *.ctest. in