godot/platform/linuxbsd/platform_linuxbsd_builders.py

"""Functions used to generate source files during build time

All such functions are invoked in a subprocess on Windows to prevent build flakiness.

"""
import os
from platform_methods import subprocess_main


def make_debug_linuxbsd(target, source, env):
    os.system('objcopy --only-keep-debug {0} {0}.debugsymbols'.format(target[0]))
    os.system('strip --strip-debug --strip-unneeded {0}'.format(target[0]))
    os.system('objcopy --add-gnu-debuglink={0}.debugsymbols {0}'.format(target[0]))


if __name__ == '__main__':
    subprocess_main(globals())
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 22:23:55 +00:00			`"""Functions used to generate source files during build time`

			`All such functions are invoked in a subprocess on Windows to prevent build flakiness.`

			`"""`
			`import os`
			`from platform_methods import subprocess_main`


Effective DisplayServer separation, rename X11 -> LinuxBSD 2020-03-03 13:36:29 +00:00			`def make_debug_linuxbsd(target, source, env):`
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 22:23:55 +00:00			`os.system('objcopy --only-keep-debug {0} {0}.debugsymbols'.format(target[0]))`
			`os.system('strip --strip-debug --strip-unneeded {0}'.format(target[0]))`
			`os.system('objcopy --add-gnu-debuglink={0}.debugsymbols {0}'.format(target[0]))`


			`if __name__ == '__main__':`
			`subprocess_main(globals())`