linter-gcc

Now with linting on-the-fly! This is a new feature so please open an issue if you encounter any problems.

Important info for Mac OSX users!

If you have XCode installed on OSX, the gcc/g++ commands will both link to clang. This can cause issues with the -fmax-errors option used by linter-gcc, which isn't recognised by clang. To properly install GCC, you need to install it with Homebrew (instructions here).

Linter in action!

Using CMake compile settings

linter-gcc can take compile settings from CMake. Using my gtf2tab project as an example, this is what you need to do:

git clone https://github.com/hebaishi/gtf2tab

cd gtf2tab

mkdir build

cd build

cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=1 ..

Running cmake with the -DCMAKE_EXPORT_COMPILE_COMMANDS flag generates a compile_commands.json file which linter-gcc can get the compile settings from. Then you simply open the project in Atom, and enter ./build/compile_commands.json in the Compile Commands File setting of linter-gcc. Note that if you supply a valid compile_commands.json file, your include paths and compile flags configuration settings (described below) are ignored.

File/Project-Specific settings

Assuming you have the a file called sample.cpp open, linter-gcc performs the following actions:

Looks for file called sample.cpp.gcc-flags.json in the same directory as your source file (file-specific settings)

Looks for a file called .gcc-flags.json in every subdirectory from the current up to your project root (subdirectory/project-specific settings)

If no .gcc-flags.json is found, the settings in your configuration page are used.

The package takes its settings from the first configuration file that is found.

You can specify your settings in .gcc-flags.json, at any level (file/subdirectory/project) using the following syntax:

{

"execPath":"/usr/bin/g++",

"gccDefaultCFlags":"-Wall",

"gccDefaultCppFlags":"-Wall -std=c++11",

"gccErrorLimit":15,

"gccIncludePaths":".,./include,./path",

"gccSuppressWarnings":true

}

Note that the include paths need to be separated by commas. If this file is present, it will replace the settings you specified in the settings window. Relative paths (starting with . or ..) are expanded with respect to the root folder. Both execPath and gccIncludePaths are expanded.

In order to avoid unwanted behavior associated with having multiple projects open, only the paths within the first project are used, and the package limits its search to 30 levels when looking for a configuration file. You can work with multiple projects, as long as each is open in a separate window. Additionally, within each project, you may have as many file/directory-specific configuration files as you wish.