mesa/src/compiler/glsl/glcpp at ed57666a5c10a601b89868fa986d9ef215b908ed - fdo-mirrors/mesa

mirror of https://gitlab.freedesktop.org/mesa/mesa.git synced 2026-01-08 21:30:23 +01:00

History

Ella-0 a18ac347cf glsl: build without bison Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8739>		2021-04-13 19:12:48 +00:00
..
tests	glsl/tests: Use exit code 126 to detect valgrind errors	2021-03-19 08:50:38 +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	glcpp: Fully initialize struct gl_context	2021-03-19 08:50:37 +00:00
glcpp.h	glsl: add preprocessor #include support	2019-11-20 05:05:55 +00:00
meson.build	glsl: build without bison	2021-04-13 19:12:48 +00:00
pp.c	glcpp: Fix undefined behaviour in glcpp	2021-03-25 00:23:43 +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).