SublimeLinter plugin for glslangValidator
- Total 1K
- Win 691
- Mac 428
- Linux 273
|May 30||May 29||May 28||May 27||May 26||May 25||May 24||May 23||May 22||May 21||May 20||May 19||May 18||May 17||May 16||May 15||May 14||May 13||May 12||May 11||May 10||May 9||May 8||May 7||May 6||May 5||May 4||May 3||May 2||May 1||Apr 30||Apr 29||Apr 28||Apr 27||Apr 26||Apr 25||Apr 24||Apr 23||Apr 22||Apr 21||Apr 20||Apr 19||Apr 18||Apr 17||Apr 16|
This linter plugin for SublimeLinter provides an interface to glslangValidator. It will be used with files that have the “glsl” and “essl” syntax provided by the SublimeText plugin OpenGL Shading Language (GLSL). It allows you to compile the shader code for a single shader using the Kronos Reference-Compiler and view the errors as annotations to your code without having to create an OpenGL context.
- glslangValidator in path
- SublimeLinter 3 plugin
- this plugin
- Use correct file-extension(.vert, .frag, …)
SublimeLinter 3 must be installed in order to use this plugin. If SublimeLinter 3 is not installed, please follow the instructions here.
Before using this plugin, you must ensure that
glslangValidator is installed on your system. To install
glslangValidator, do the following:
- Got to Kronos GLSL Reference-Compiler.
- Either pick a binary to install (currently provided for Windows & Linux) or
- Download the source and compile & install it (currently only option for OSX - but no worries, it comes with CMake and worked out of the box for me)
- Ensure it's in your path, e.g.
glslangValidatorin a terminal produces not an error.
In order for
glslangValidator 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
glslangValidator, you can proceed to install the SublimeLinter-contrib-glslangValidator plugin if it is not yet installed.
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:
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.
When the plugin list appears, type
glslangValidator. Among the entries you should see
SublimeLinter-contrib-glslangValidator. If that entry is not highlighted, use the keyboard or mouse to select it.
- Currently only error-messages are parsed. If somebody has a good example I'm more than willing to add it.
- Use the appropriate file-extension glslangValidator expects:
.vertfor a vertex shader
.tescfor a tessellation control shader
.tesefor a tessellation evaluation shader
.geomfor a geometry shader
.fragfor a fragment shader
.compfor a compute shader
For general information on how SublimeLinter works with settings, please see Settings. For information on generic linter settings, please see Linter Settings.
If you would like to contribute enhancements or fixes, please do the following:
- Fork the plugin repository.
- Hack on a separate topic branch created from the latest
- Commit and push the topic branch.
- Make a pull request.
- 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!