Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Common Issues

Jump to bottom
Emerson Knapp edited this page Sep 11, 2017 · 7 revisions

Note for Mac OSX Users:

If you intend to use linter-gcc on OSX, you need to install GCC using Homebrew. The gcc/g++ commands that are available after installing XCode actually point to clang. Please see this issue for more information.

Note for Windows Users:

Getting linter-gcc working on Windows requires a bit more work. Please read the Windows users guide for more detailed information.

Checklist

  • Ensure that you have GCC installed. You can do this by entering the following command into a terminal/command prompt:
gcc --version
  • Ensure that you have the base linter installed. linter-gcc went through a re-write for version 0.6.0 to enable linting on-the-fly, and the automatic installation of package dependencies was temporarily removed. It was re-introduced again in version 0.6.6. To install the base linter, enter the following command into a temrinal/command prompt:
apm install linter

  • Ensure that your TextEditor grammar is C/C++/C++14. linter-gcc will not work with any other grammar

  • If after following the above steps you are still experiencing problems kindly do the following:

  1. enable the Debugging Messages option in the package configuration page
  2. Open the Developer Console in Atom (with Cmd+Shift+I or Ctrl+Shift+I)
  3. Open an issue, reporting your linter-gcc version, the linter-gcc messages that appear in the developer console, and the nature of the problem.
  • To avoid generating .o files everywhere, just add -o /dev/null to your command-line options on Linux and -o NUL on Windows.
Clone this wiki locally