mesa/src/glsl/glcpp
Kenneth Graunke 603940d5bb glcpp: Automatically #define GL_core_profile 1 on GLSL 1.50+.
Page 17 of the GLSL 1.50.11 specification states:
"There is a built-in macro definition for each profile the
 implementation supports.  All implementations provide the following
 macro:

Reviewed-by: Matt Turner <mattst88@gmail.com>
Signed-off-by: Kenneth Graunke <kenneth@whitecape.org>
2013-06-10 10:54:56 -07:00
..
tests glcpp: Add test case for recently fixed loop-control underflow bug. 2013-06-03 13:33:32 -07:00
.gitignore glcpp: Add back tests/*.out to .gitignore 2013-01-11 11:49:33 +01:00
glcpp-lex.l glcpp: Reject token pasting operator in GLES 2013-01-11 10:57:25 -08:00
glcpp-parse.y glcpp: Automatically #define GL_core_profile 1 on GLSL 1.50+. 2013-06-10 10:54:56 -07:00
glcpp.c glcpp: Add --disable-line-continuations argument to standalone glcpp 2013-01-11 13:55:41 -08:00
glcpp.h glcpp: Accept pointer to GL context rather than just the API version 2013-01-11 13:55:41 -08:00
pp.c glcpp: Fix post-decrement underflow in loop-control variable 2013-06-03 13:33:31 -07:00
README glcpp: Update README for new support of __LINE__ and __FILE__. 2012-11-29 13:03:02 -08:00

glcpp -- GLSL "C" preprocessor

This is a simple preprocessor designed to provide the preprocessing
needs of the GLSL language. The requirements for this preprocessor are
specified in the GLSL 1.30 specification availble from:

http://www.opengl.org/registry/doc/GLSLangSpec.Full.1.30.10.pdf

This specification is not precise on some semantics, (for example,
#define and #if), defining these merely "as is standard for C++
preprocessors". To fill in these details, I've been using a draft of
the C99 standard as available from:

http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdf

Any downstream compiler accepting output from glcpp should be prepared
to encounter and deal with the following preprocessor macros:

	#line
	#pragma
	#extension

All other macros will be handled according to the GLSL specification
and will not appear in the output.

Known limitations
-----------------
A file that ends with a function-like macro name as the last
non-whitespace token will result in a parse error, (where it should be
passed through as is).