virtualx-engine/platform/x11/SCsub

#!/usr/bin/env python

import os
Import('env')

def make_debug(target, source, env):
    os.system('objcopy --only-keep-debug %s %s.debugsymbols' % (target[0], target[0]))
    os.system('strip --strip-debug --strip-unneeded %s' % (target[0]))
    os.system('objcopy --add-gnu-debuglink=%s.debugsymbols %s' % (target[0], target[0]))

common_x11 = [
    "context_gl_x11.cpp",
    "crash_handler_x11.cpp",
    "os_x11.cpp",
    "key_mapping_x11.cpp",
    "joypad_linux.cpp",
    "power_x11.cpp",
]

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

if env["debug_symbols"] == "full" or env["debug_symbols"] == "yes":
    env.AddPostAction(prog, make_debug)
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`

Create separate debug info files by default Now that we have a built-in stacktrace on a segfault it would be useful to have debug information on debug_release builds so that bugreports can include this information. Without this debug info we will still get function names in the backtrace but not file location. This commit will by default build all targets with minimal debug info and then strip the information into separate files. On MacOS this is a .dSYM file, on Linux/MingW this is a .debug file. MacOSX will automatically load a dSYM file if it exists in its debugger. On Linux/MingW we create a 'gnu debuglink' meaning that gdb and friends will automatically find the debug symbols if they exist. Existing workflow for developers does not change at all, except that we now create two instead of one build artifact by default. This commit also adds a 'debug_symbols' option to X11, MacOS, and MingW targets. The default is 'yes' which corresponds to -g1. The alternatives are 'no' (don't generate debug infos at all) or 'full' which runs with -g2. A target=debug build will now build with -g3. 2017-09-13 19:32:24 +02:00			`import os`
GODOT IS OPEN SOURCE 2014-02-10 02:10:30 +01:00			`Import('env')`

Create separate debug info files by default Now that we have a built-in stacktrace on a segfault it would be useful to have debug information on debug_release builds so that bugreports can include this information. Without this debug info we will still get function names in the backtrace but not file location. This commit will by default build all targets with minimal debug info and then strip the information into separate files. On MacOS this is a .dSYM file, on Linux/MingW this is a .debug file. MacOSX will automatically load a dSYM file if it exists in its debugger. On Linux/MingW we create a 'gnu debuglink' meaning that gdb and friends will automatically find the debug symbols if they exist. Existing workflow for developers does not change at all, except that we now create two instead of one build artifact by default. This commit also adds a 'debug_symbols' option to X11, MacOS, and MingW targets. The default is 'yes' which corresponds to -g1. The alternatives are 'no' (don't generate debug infos at all) or 'full' which runs with -g2. A target=debug build will now build with -g3. 2017-09-13 19:32:24 +02:00			`def make_debug(target, source, env):`
Rename the debug symbol files to .debugsymbols Some users were confused by the '.debug' suffix for the symbols. 2017-12-16 13:54:14 +01:00			`os.system('objcopy --only-keep-debug %s %s.debugsymbols' % (target[0], target[0]))`
Create separate debug info files by default Now that we have a built-in stacktrace on a segfault it would be useful to have debug information on debug_release builds so that bugreports can include this information. Without this debug info we will still get function names in the backtrace but not file location. This commit will by default build all targets with minimal debug info and then strip the information into separate files. On MacOS this is a .dSYM file, on Linux/MingW this is a .debug file. MacOSX will automatically load a dSYM file if it exists in its debugger. On Linux/MingW we create a 'gnu debuglink' meaning that gdb and friends will automatically find the debug symbols if they exist. Existing workflow for developers does not change at all, except that we now create two instead of one build artifact by default. This commit also adds a 'debug_symbols' option to X11, MacOS, and MingW targets. The default is 'yes' which corresponds to -g1. The alternatives are 'no' (don't generate debug infos at all) or 'full' which runs with -g2. A target=debug build will now build with -g3. 2017-09-13 19:32:24 +02:00			`os.system('strip --strip-debug --strip-unneeded %s' % (target[0]))`
Rename the debug symbol files to .debugsymbols Some users were confused by the '.debug' suffix for the symbols. 2017-12-16 13:54:14 +01:00			`os.system('objcopy --add-gnu-debuglink=%s.debugsymbols %s' % (target[0], target[0]))`
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 = [`
			`"context_gl_x11.cpp",`
			`"crash_handler_x11.cpp",`
			`"os_x11.cpp",`
			`"key_mapping_x11.cpp",`
			`"joypad_linux.cpp",`
			`"power_x11.cpp",`
GODOT IS OPEN SOURCE 2014-02-10 02:10:30 +01:00			`]`

disable caching for targets using helper functions 2017-11-28 21:27:57 +01:00			`prog = env.add_program('#bin/godot', ['godot_x11.cpp'] + common_x11)`
use the same cache for all branches for appveyor 2017-11-27 14:39:05 +01:00
Create separate debug info files by default Now that we have a built-in stacktrace on a segfault it would be useful to have debug information on debug_release builds so that bugreports can include this information. Without this debug info we will still get function names in the backtrace but not file location. This commit will by default build all targets with minimal debug info and then strip the information into separate files. On MacOS this is a .dSYM file, on Linux/MingW this is a .debug file. MacOSX will automatically load a dSYM file if it exists in its debugger. On Linux/MingW we create a 'gnu debuglink' meaning that gdb and friends will automatically find the debug symbols if they exist. Existing workflow for developers does not change at all, except that we now create two instead of one build artifact by default. This commit also adds a 'debug_symbols' option to X11, MacOS, and MingW targets. The default is 'yes' which corresponds to -g1. The alternatives are 'no' (don't generate debug infos at all) or 'full' which runs with -g2. A target=debug build will now build with -g3. 2017-09-13 19:32:24 +02:00			`if env["debug_symbols"] == "full" or env["debug_symbols"] == "yes":`
use the same cache for all branches for appveyor 2017-11-27 14:39:05 +01:00			`env.AddPostAction(prog, make_debug)`