fdo-mirrors/mesa
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/mesa/mesa.git synced 2026-01-15 13:50:29 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 2
mesa/src/compiler/glsl/glcpp
History
Mike Blumenkrantz f9ae947e72 meson: add enable-glcpp-tests option 
these are too intermittent to be left enabled on CI for now

Reviewed-by: Eric Anholt <eric@anholt.net>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8738>
2021-01-28 15:52:32 +00:00
..
tests glcpp: Handle bison-3.6 error message changes 2020-11-19 15:31:15 +00:00
glcpp-lex.l glsl: add preprocessor #include support 2019-11-20 05:05:55 +00:00
glcpp-parse.y glsl: add extra pp tokens workaround and enable for CoR 2020-10-29 23:35:58 +00:00
glcpp.c Fix scons build 2018-04-12 19:55:01 -04:00
glcpp.h glsl: add preprocessor #include support 2019-11-20 05:05:55 +00:00
meson.build meson: add enable-glcpp-tests option 2021-01-28 15:52:32 +00:00
pp.c glsl: pass gl_context to glcpp_parser_create() 2019-11-20 05:05:55 +00:00
pp_standalone_scaffolding.c mesa: add support cursor support for relative path shader includes 2019-11-20 05:05:56 +00:00
pp_standalone_scaffolding.h mesa: add support cursor support for relative path shader includes 2019-11-20 05:05:56 +00:00
README

README 

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).