A Visual Studio Code extension supporting a number of static code analyzers for C and C++ code.
- On-the-fly linting within the code editor, upon file save or after file edits.
- Automatically finds available static analysis tools.
- Easily supports additional static analyzers with minimum development effort.
At least one of the above static code analyzers must be installed on your machine(s).
The extension should support any versions of the listed static code
analyzers; and will attempt to locate them within your PATH
environment variable.
If a tool is not automatically found, the appropriate
c-cpp-flylint.*.executable
configuration must be specified manually.
Windows users may download and install the static code analyzers from the listed URLs mentioned elsewhere in this documentation.
If PC-lint has been installed, be certain to use the Flexelint
configuration sections, specifying the full path and filename
of PC-lint as the c-cpp-flylint.flexelint.executable
configuration option.
Clang is available via apt-get
:
# sudo apt-get install clang
CppCheck is available via apt-get
:
# sudo apt-get install cppcheck
Flexelint is commercial software; however, it may be obtained from the URL mentioned elsewhere in this documentation.
For macOS users, Clang is already included when Xcode and its' CLI tools are installed.
For macOS users, CppCheck can most easily be installed through Homebrew.
# brew install cppcheck
Flexelint is commercial software; however, it may be obtained from the URL mentioned elsewhere in this documentation.
Due to the large quantity of configuration options -- in tandem with the ever growing number of supported static code analyzers -- all configuration options are not documented here.
However, every configuration option is well documented within
File -> Preferences -> Settings [alternatively, one of the
keybindings: Command+,
or Ctrl+,
].
- run
npm install
oryarn install
inside thec-cpp-flylint
andc-cpp-flylint-server
folders. - open multiple VS Code instances, with one rooted inside folder
c-cpp-flylint
and another rooted inside folderc-cpp-flylint-server
.
- open VS Code rooted inside the folder
c-cpp-flylint-server
. - run
npm run test
to execute the unit-tests for all linters. - run
npm run compile
ornpm run watch
to build the server and it will compile it into thec-cpp-flylint
folder. - to debug press F5 which attaches a debugger to the server.
- open VS Code rooted inside the folder
c-cpp-flylint
. - run F5 to build and debug the whole (client with the server) extension.
Both the source code and issue tracker are hosted at GitHub.
For support purposes, please visit the above URL and select from the Issue and/or Pull Request areas.
Copyright (C) 2017 Joseph Benden.
Licensed under the MIT License.