Easy real time C++ syntax check and intellisense if you use CMake
Emacs Lisp Shell
Pull request Compare This branch is 79 commits behind redguardtoo:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.gitignore
README.org
cpputils-cmake-pkg.el
cpputils-cmake.el
pkg.sh

README.org

cpputils-cmake.el (version 0.4.5)

cpputils-cmake automatically enable real time syntax check (Flymake) and IntelliSense (auto-complete+auto-complete-clang, company-mode) if you use CMake.

It does all the configuration dirty job automatically for you. So you can use Flymake, auto-complete, auto-complete-clang, company-mode, compile, ff-find-other-file (if you press `C-x C-o` in C/C++ file, ff-find-other-file will open correct header file under cursor) with almost no configuration.

Key points before you continue:

  • It’s lightweight.
  • easy to use, copy the elisp code from “Set up” section into you ~/.emacs. DONE! Use Emacs as usual and ignore advanced tips in remaining sections.
  • cpputils-cmake will configure many third party plugins automatically for you. But it’s NOT dependent on those plugins. Only CMake is required.

install

easy way

cpputils-cmake is already uploaded to http://marmalade-repo.org/. So the best way to install it is using Emacs’ package manager.

manual way

If you don’t want to use package manager, you only need download the file cpputils-cmake.el and put it somewhere (say ~/.emacs/lisp), then add below code into your .emacs:

(add-to-list 'load-path "~/.emacs.d/lisp/")
(require 'cpputils-cmake)

set up

Copy and paste below code into your .emacs:

(add-hook 'c-mode-hook (lambda () (cppcm-reload-all)))
(add-hook 'c++-mode-hook (lambda () (cppcm-reload-all)))
;; OPTIONAL, somebody reported that they can use this package with Fortran
(add-hook 'c90-mode-hook (lambda () (cppcm-reload-all)))
;; OPTIONAL, avoid typing full path when starting gdb
(global-set-key (kbd "C-c C-g")
 '(lambda ()(interactive) (gud-gdb (concat "gdb --fullname " (cppcm-get-exe-path-current-buffer)))))

one minute step by step tutorial

one line bash to create “hello” project

mkdir -p hello/src;printf "#include <stdio.h>\nint main(void) {\nprintf(\"hello world\");\nreturn 0;\n}" > hello/src/main.cpp;printf "cmake_minimum_required(VERSION 2.6)\nadd_executable(main main.cpp)" > hello/src/CMakeLists.txt

use cmake as usual

Please note you need run “Make” at least once before using cpputils-cmake:

mkdir hello/build;cd hello/build;cmake ../src;make clean;make

If you use another directory name like “mybuild” instead of “build”, you must add following line into your .emacs:

(setq cppcm-build-dirname "mybuild")

flymake

Run “M-x flymake-mode”.

Now typing some random code and watch the real time hint on your syntax errors.

compile

Compile the program: `M-x compile`

You can see the default command line displayed in minibuffer is `make -C ~/your-projects-blah-blah/hello/build`

BTW, you can also run the command `M-x cppcm-compile` to compile the current excutable only.

You can see the actual command displayed in minibuffer is `make -C ~/your-project-blah-blah/hello/build/sub-project-dir-if-your-are-editing-its-cpp-file`

start gdb

Press hot key `C-c C-g` (suppose you’ve copied my configuration from previous section).

You can see the gud-gdb starts and the executable “~/your-projects-blah-blah/hello/build/main” is loaded automatically.

auto-complete & auto-complete-clang (OPTIONAL)

Use them as usual. You can see that the Intellisense/auto-complete is more precise.

company-mode (OPTIONAL)

Use them as usual. You can see that the Intellisense/auto-complete is more precise.

open header file

Press the hot key `C-x C-o` or `M-x ff-find-other-file`. The corresponding header file is opened correctly.

This is the default feature of Emacs. What cpputils-cmake does is set up the directories of those header files for you automatically so that the header files could be found by Emacs.

tips

get full path of target

The command “cppcm-get-exe-path-current-buffer” will copy the current executable into the kill ring and OS clipboard.

You need install `xsel` under Linux to support OS clipboard.

This could be very useful if you want to access the directory of the executable as quickly as possible.

You can yank (paste) the full path to the eshell or minibuffer and press “M-backspace” to get the directory name.

reload cpputils-cmake

You can always `M-x cppcm-reload-all` any time.

There is also `cppcm-reload-all-hook` which will be called after `cppcm-reload-all`. This give you a chance to tweak or override the set up.

Here is the list of global variables third party plugins will use (and you can tweak):

variable nameplugin/command name
ac-clang-flagsauto-complete-clang
company-clang-argumentscompany-mode
cc-search-directoriesff-find-other-file

Currently `auto-complete-clang` use global variable `ac-clang-flags`. `company-mode` use `company-clang-arguments`.

compile only current target

“M-x cppcm-compile”.

Please press “C-h v cppcm-compile-list” for other compile options.

make clean && make

“M-x cppcm-recompile”

contact me

You can report bugs at https://github.com/redguardtoo/cpputils-cmake. My email is <chenbin DOT sh AT gmail>.

Please use github issue tracker instead of email me directly if you want my response ASAP. It’s because github will email me any issue you submit. The github email will be put into my “IMPORTANT” folder automatically. But regular email in my “INBOX” folder will be mixed with spams. I got lots of spams these days.

license

Copyright (C) 2012 Chen Bin

Author: Chen Bin <chenbin DOT sh AT gmail DOT com> Keywords: flymake IntelliSense cmake

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.