virtualx-engine/drivers/gles3/shaders/SCsub

#!/usr/bin/env python

Import("env")

if "GLES3_GLSL" in env["BUILDERS"]:
    env.GLES3_GLSL("copy.glsl")
    env.GLES3_GLSL("resolve.glsl")
    env.GLES3_GLSL("canvas.glsl")
    env.GLES3_GLSL("canvas_shadow.glsl")
    env.GLES3_GLSL("scene.glsl")
    env.GLES3_GLSL("cubemap_filter.glsl")
    env.GLES3_GLSL("cube_to_dp.glsl")
    env.GLES3_GLSL("blend_shape.glsl")
    env.GLES3_GLSL("screen_space_reflection.glsl")
    env.GLES3_GLSL("effect_blur.glsl")
    env.GLES3_GLSL("subsurf_scattering.glsl")
    env.GLES3_GLSL("ssao.glsl")
    env.GLES3_GLSL("ssao_minify.glsl")
    env.GLES3_GLSL("ssao_blur.glsl")
    env.GLES3_GLSL("exposure.glsl")
    env.GLES3_GLSL("tonemap.glsl")
    env.GLES3_GLSL("particles.glsl")
    env.GLES3_GLSL("lens_distorted.glsl")
BuildSystem: generated files have .gen.extension 2017-06-23 17:03:41 +02:00			`#!/usr/bin/env python`

SCons: Format buildsystem files with psf/black Configured for a max line length of 120 characters. psf/black is very opinionated and purposely doesn't leave much room for configuration. The output is mostly OK so that should be fine for us, but some things worth noting: - Manually wrapped strings will be reflowed, so by using a line length of 120 for the sake of preserving readability for our long command calls, it also means that some manually wrapped strings are back on the same line and should be manually merged again. - Code generators using string concatenation extensively look awful, since black puts each operand on a single line. We need to refactor these generators to use more pythonic string formatting, for which many options are available (`%`, `format` or f-strings). - CI checks and a pre-commit hook will be added to ensure that future buildsystem changes are well-formatted. (cherry picked from commit cd4e46ee65dab6baa6a143bf3b3f64244be36712) 2020-03-30 08:28:32 +02:00			`Import("env")`
Begining of GLES3 renderer: -Most 2D drawing is implemented -Missing shaders -Missing all 3D -Editor needs to be set on update always to be used, otherwise it does not refresh -Large parts of editor not working 2016-10-03 21:33:42 +02:00
SCons: Format buildsystem files with psf/black Configured for a max line length of 120 characters. psf/black is very opinionated and purposely doesn't leave much room for configuration. The output is mostly OK so that should be fine for us, but some things worth noting: - Manually wrapped strings will be reflowed, so by using a line length of 120 for the sake of preserving readability for our long command calls, it also means that some manually wrapped strings are back on the same line and should be manually merged again. - Code generators using string concatenation extensively look awful, since black puts each operand on a single line. We need to refactor these generators to use more pythonic string formatting, for which many options are available (`%`, `format` or f-strings). - CI checks and a pre-commit hook will be added to ensure that future buildsystem changes are well-formatted. (cherry picked from commit cd4e46ee65dab6baa6a143bf3b3f64244be36712) 2020-03-30 08:28:32 +02:00			`if "GLES3_GLSL" in env["BUILDERS"]:`
			`env.GLES3_GLSL("copy.glsl")`
			`env.GLES3_GLSL("resolve.glsl")`
			`env.GLES3_GLSL("canvas.glsl")`
			`env.GLES3_GLSL("canvas_shadow.glsl")`
			`env.GLES3_GLSL("scene.glsl")`
			`env.GLES3_GLSL("cubemap_filter.glsl")`
			`env.GLES3_GLSL("cube_to_dp.glsl")`
			`env.GLES3_GLSL("blend_shape.glsl")`
			`env.GLES3_GLSL("screen_space_reflection.glsl")`
			`env.GLES3_GLSL("effect_blur.glsl")`
			`env.GLES3_GLSL("subsurf_scattering.glsl")`
			`env.GLES3_GLSL("ssao.glsl")`
			`env.GLES3_GLSL("ssao_minify.glsl")`
			`env.GLES3_GLSL("ssao_blur.glsl")`
			`env.GLES3_GLSL("exposure.glsl")`
			`env.GLES3_GLSL("tonemap.glsl")`
			`env.GLES3_GLSL("particles.glsl")`
			`env.GLES3_GLSL("lens_distorted.glsl")`