c5bd0c37ce
- 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.
23 lines
530 B
Python
23 lines
530 B
Python
#!/usr/bin/env python
|
|
|
|
import os
|
|
Import('env')
|
|
|
|
from platform_methods import run_in_subprocess
|
|
import platform_osx_builders
|
|
|
|
files = [
|
|
'crash_handler_osx.mm',
|
|
'os_osx.mm',
|
|
'godot_main_osx.mm',
|
|
'sem_osx.cpp',
|
|
'dir_access_osx.mm',
|
|
'joypad_osx.cpp',
|
|
'power_osx.cpp',
|
|
]
|
|
|
|
prog = env.add_program('#bin/godot', files)
|
|
|
|
if (env["debug_symbols"] == "full" or env["debug_symbols"] == "yes") and env["separate_debug_symbols"]:
|
|
env.AddPostAction(prog, run_in_subprocess(platform_osx_builders.make_debug_osx))
|
|
|