virtualx-engine/platform/linuxbsd/SCsub

#!/usr/bin/env python

Import("env")

from platform_methods import run_in_subprocess
import platform_linuxbsd_builders

common_x11 = [
    "crash_handler_linuxbsd.cpp",
    "os_linuxbsd.cpp",
    "joypad_linux.cpp",
    "context_gl_x11.cpp",
    "detect_prime_x11.cpp",
    "display_server_x11.cpp",
    "vulkan_context_x11.cpp",
    "key_mapping_x11.cpp",
]

prog = env.add_program("#bin/godot", ["godot_linuxbsd.cpp"] + common_x11)

if (env["debug_symbols"] == "full" or env["debug_symbols"] == "yes") and env["separate_debug_symbols"]:
    env.AddPostAction(prog, run_in_subprocess(platform_linuxbsd_builders.make_debug_linuxbsd))
SCsub: Add python shebang as a hint for syntax highlighting Also switch existing shebangs to "better" /usr/bin/env python. 2016-10-17 08:50:25 +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. 2020-03-30 08:28:32 +02:00			`Import("env")`
GODOT IS OPEN SOURCE 2014-02-10 02:10:30 +01:00
Running builder (content generator) functions in subprocesses on Windows - Refactored all builder (make_) functions into separate Python modules along to the build tree - Introduced utility function to wrap all invocations on Windows, but does not change it elsewhere - Introduced stub to use the builders module as a stand alone script and invoke a selected function There is a problem with file handles related to writing generated content (.gen.h and *.gen.cpp) on Windows, which randomly causes a SHARING VIOLATION error to the compiler resulting in flaky builds. Running all such content generators in a new subprocess instead of directly inside the build script works around the issue. Yes, I tried the multiprocessing module. It did not work due to conflict with SCons on cPickle. Suggested workaround did not fully work either. Using the run_in_subprocess wrapper on osx and x11 platforms as well for consistency. In case of running a cross-compilation on Windows they would still be used, but likely it will not happen in practice. What counts is that the build itself is running on which platform, not the target platform. Some generated files are written directly in an SConstruct or SCsub file, before the parallel build starts. They don't need to be written in a subprocess, apparently, so I left them as is. 2018-03-17 23:23:55 +01:00			`from platform_methods import run_in_subprocess`
Effective DisplayServer separation, rename X11 -> LinuxBSD 2020-03-03 14:36:29 +01:00			`import platform_linuxbsd_builders`
GODOT IS OPEN SOURCE 2014-02-10 02:10:30 +01:00
Added a crash handler to dump the backtrace on Windows, Linux and OS X 2017-09-08 03:01:49 +02:00			`common_x11 = [`
Effective DisplayServer separation, rename X11 -> LinuxBSD 2020-03-03 14:36:29 +01:00			`"crash_handler_linuxbsd.cpp",`
			`"os_linuxbsd.cpp",`
			`"joypad_linux.cpp",`
Add runtime GLES2 / Vulkan context selection. 2019-07-12 15:18:30 +02:00			`"context_gl_x11.cpp",`
Effective DisplayServer separation, rename X11 -> LinuxBSD 2020-03-03 14:36:29 +01:00			`"detect_prime_x11.cpp",`
			`"display_server_x11.cpp",`
Initial work on Vulkan: -Added VulkanContext -Added an X11 implementation -Added a rendering device abstraction -added a Vulkan rendering device abstraction -Engine does not work, only shows Godot logo (run it from bin/) 2019-06-07 18:07:57 +02:00			`"vulkan_context_x11.cpp",`
Added a crash handler to dump the backtrace on Windows, Linux and OS X 2017-09-08 03:01:49 +02:00			`"key_mapping_x11.cpp",`
GODOT IS OPEN SOURCE 2014-02-10 02:10:30 +01: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. 2020-03-30 08:28:32 +02:00			`prog = env.add_program("#bin/godot", ["godot_linuxbsd.cpp"] + common_x11)`
use the same cache for all branches for appveyor 2017-11-27 14:39:05 +01:00
Make separate debug symbols opt-in This adds a separate_debug_symbols option to the x11, windows, and osx targets. This will default to adding normal debugging symbols to the artifacts and only splits them when separate_debug_symbols=yes on the Scons command line. 2018-01-26 20:46:56 +01:00			`if (env["debug_symbols"] == "full" or env["debug_symbols"] == "yes") and env["separate_debug_symbols"]:`
Effective DisplayServer separation, rename X11 -> LinuxBSD 2020-03-03 14:36:29 +01:00			`env.AddPostAction(prog, run_in_subprocess(platform_linuxbsd_builders.make_debug_linuxbsd))`