ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Sublime​Linter-cppcheck

by SublimeLinter ST3

This linter plugin for SublimeLinter provides an interface to cppcheck.

Details

Installs

  • Total 24K
  • Win 10K
  • OS X 5K
  • Linux 8K
Dec 12 Dec 11 Dec 10 Dec 9 Dec 8 Dec 7 Dec 6 Dec 5 Dec 4 Dec 3 Dec 2 Dec 1 Nov 30 Nov 29 Nov 28 Nov 27 Nov 26 Nov 25 Nov 24 Nov 23 Nov 22 Nov 21 Nov 20 Nov 19 Nov 18 Nov 17 Nov 16 Nov 15 Nov 14 Nov 13 Nov 12 Nov 11 Nov 10 Nov 9 Nov 8 Nov 7 Nov 6 Nov 5 Nov 4 Nov 3 Nov 2 Nov 1 Oct 31 Oct 30 Oct 29 Oct 28
Windows 10 13 11 8 6 17 11 16 11 11 12 7 18 19 16 8 11 16 8 15 8 11 11 8 8 9 14 14 10 12 12 7 15 11 15 12 11 9 15 15 10 10 9 11 15 9
OS X 4 6 6 3 4 3 5 0 4 3 5 8 2 11 3 6 2 3 1 3 4 5 4 4 2 8 4 5 9 4 3 7 3 5 8 4 4 3 3 3 4 4 9 3 5 7
Linux 1 12 3 1 4 10 10 12 9 5 5 6 13 13 6 6 6 3 6 9 4 7 11 8 7 4 8 7 6 4 6 11 12 10 12 7 10 15 5 9 4 7 5 15 12 5

Readme

Source
raw.​githubusercontent.​com

SublimeLinter-cppcheck

Build Status

This linter plugin for SublimeLinter provides an interface to cppcheck. It will be used with files that have the “C++” or “C” syntax.

Installation

SublimeLinter 3 must be installed in order to use this plugin. If SublimeLinter 3 is not installed, please follow the instructions here.

Linter installation

Before using this plugin, you must ensure that cppcheck is installed on your system. To install cppcheck, do one of the following:

  • Install cppcheck from your favorite package manager by typing the following in a terminal:
<package manager> install cppcheck

Once cppcheck is installed, you must ensure it is in your system PATH so that SublimeLinter can find it. This may not be as straightforward as you think, so please read about how linter executables are located in the documentation.

Linter configuration

In order for cppcheck to be executed by SublimeLinter, you must ensure that its path is available to SublimeLinter. Before going any further, please read and follow the steps in “Finding a linter executable” through “Validating your PATH” in the documentation.

Once you have installed and configured cppcheck, you can proceed to install the SublimeLinter-cppcheck plugin if it is not yet installed.

Plugin installation

Please use Package Control to install the linter plugin. This will ensure that the plugin will be updated when new versions are available. If you want to install from source so you can modify the source code, you probably know what you are doing so we won’t cover that here.

To install via Package Control, do the following:

  1. Within Sublime Text, bring up the Command Palette and type install. Among the commands you should see Package Control: Install Package. If that command is not highlighted, use the keyboard or mouse to select it. There will be a pause of a few seconds while Package Control fetches the list of available plugins.

  2. When the plugin list appears, type cppcheck. Among the entries you should see SublimeLinter-cppcheck. If that entry is not highlighted, use the keyboard or mouse to select it.

Settings

For general information on how SublimeLinter works with settings, please see Settings. For information on generic linter settings, please see Linter Settings.

In addition to the standard SublimeLinter settings, SublimeLinter-cppcheck provides its own settings. Those marked as “Inline Setting” or “Inline Override” may also be used inline.

Setting Description Inline Setting Inline Override
std Set the language standard used.
enable A comma-delimited list of checks to enable. Defaults to style.

Examples

For enable, you can use a single string (ex: "style,unusedFunction"), or an array of strings if not inline (ex: ["style", "unusedFunction"]).

For std, you can use a single string for a single value, but you have to use an array of strings for multiple values (ex. ["c89", "c99"]), which means you can't use multiple values in inline settings.

Contributing

If you would like to contribute enhancements or fixes, please do the following:

  1. Fork the plugin repository.
  2. Hack on a separate topic branch created from the latest master.
  3. Commit and push the topic branch.
  4. Make a pull request.
  5. Be patient. ;-)

Please note that modications should follow these coding guidelines:

  • Indent is 4 spaces.
  • Code should pass flake8 and pep257 linters.
  • Vertical whitespace helps readability, don’t be afraid to use it.
  • Please use descriptive variable names, no abbrevations unless they are very well known.

Thank you for helping out!