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

Sublime​Linter-contrib-avr-gcc

by ChisholmKyle ST3

Linter for avr-gcc

Details

Installs

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

Readme

Source
raw.​githubusercontent.​com

SublimeLinter-contrib-avr-gcc

Build Status

This linter plugin for SublimeLinter provides an interface to avr-gcc. This linter will be used with files that have the “C/C++” syntax.

Tip for usage with Arduino

If you are new to avr-gcc or microprocessors in general and want to get started using the Arduino library with C/C++ source files and great linting, this plugin can help (but does require some manual setup). See the example in Settings for using it with an Arduino Pro 5V and Wire library. If you set your Arduino IDE to show verbose output when compiling (enable in Arduino preferences), you can easily extract the required compiler flags for linting with avr-gcc.

Installation

SublimeLinter must be installed in order to use this plugin.

Please use Package Control to install the linter plugin.

Install avr-gcc

Before using this plugin, you must ensure that avr-gcc is installed on your system. To install avr-gcc, do can do the following:

Linux

  1. Install avr-gcc with your distro's package manager. On Ubuntu, for example, type the following in a terminal:
sudo apt-get install git gcc-avr

Mac

Xcode and command line tools are required.

  1. Install and update Macports
  2. Type the following in a terminal:
sudo port install avr-gcc

Alternatively, use Homebrew:

  1. Install Homebrew
  2. Run the following commands:
brew tap osx-cross/avr
    brew install avr-libc

Windows

  1. Download and extract the Microchip AVR Toolchain for Windows.

Configure PATH

In order for avr-gcc to be executed by SublimeLinter, you must ensure that its path is available to SublimeLinter. The docs cover troubleshooting PATH configuration.

Settings

Additional SublimeLinter-contrib-avr-gcc settings:

Setting Description
include_dirs A list of directories to be added to the header search paths (-I is not needed).
extra_flags A string with extra flags to pass to avr-gcc. These should be used carefully, as they may cause linting to fail.
extra_cflags Extra flags to pass to avr-gcc when linting C syntax code.
extra_cxxflags Extra flags to pass to avr-gcc when linting C++ syntax code.

In project-specific settings, note that SublimeLinter allows expansion variables. For example the variable '${project_path}' can be used to specify a path relative to the project folder in your settings. Here is an example of project settings for development targeting an Arduino Mini Pro 5V with the Wire library:

"settings": {
    "SublimeLinter.linters.avrgcc.executable": "C:/tools/avr8-gnu-toolchain-win32_x86/bin/avr-gcc.exe",
    "SublimeLinter.linters.avrgcc.extra_cflags": "-std=gnu99",
    "SublimeLinter.linters.avrgcc.extra_cxxflags": "-std=gnu++14",
    "SublimeLinter.linters.avrgcc.extra_flags": "-mmcu=atmega328p -DF_CPU=16000000L -DARDUINO_ARCH_AVR -DARDUINO_AVR_PRO",
    "SublimeLinter.linters.avrgcc.include_dirs": [
        "${project_path}/include",
        "C:/Program Files (x86)/Arduino/hardware/arduino/avr/cores/arduino",
        "C:/Program Files (x86)/Arduino/hardware/arduino/avr/variants/eightanaloginputs",
        "C:/Program Files (x86)/Arduino/hardware/arduino/avr/libraries/Wire/src",
        "C:/Program Files (x86)/Arduino/hardware/arduino/avr/libraries/Wire/src/utility"
    ]
}

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 modifications 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 abbreviations unless they are very well known.

Thank you for helping out!