mirror/godot
2
0
Fork 0
mirror of https://github.com/godotengine/godot.git synced 2025-01-12 20:22:49 +08:00
Code Issues Packages Projects Releases Wiki Activity
5307043751
godot/modules/gdnative/SCsub

49 lines
1.8 KiB
Plaintext
Raw Normal View History

added dlscript module This module was written by bojidar-bg and me, with the help of ClikCode and touilleMan. This adds a module to Godot that enables the use of dynamic libraries as a source for scripts. That also allows third party libraries to be linked to Godot more easily and without creating modules. For a readme see https://github.com/GodotNativeTools/godot_headers/blob/master/README.md
2017-04-03 22:11:38 +08:00
#!/usr/bin/env python
Import('env')
merged gdnative and nativescript module
2017-09-03 18:40:41 +08:00
gdn_env = env.Clone()
[GDnative] replace gdnative_api_struct.h by a json-based autogenerated system
2017-10-03 11:23:05 +08:00
gdn_env.add_source_files(env.modules_sources, "gdnative.cpp")
gdn_env.add_source_files(env.modules_sources, "register_types.cpp")
Add access for GDNative modules to some platform dependent internals on Android
2018-06-16 08:29:11 +08:00
gdn_env.add_source_files(env.modules_sources, "android/*.cpp")
merged gdnative and nativescript module
2017-09-03 18:40:41 +08:00
gdn_env.add_source_files(env.modules_sources, "gdnative/*.cpp")
gdn_env.add_source_files(env.modules_sources, "nativescript/*.cpp")
Add plugin to edit GDNativeLibrary Rename GDNativeLibraryEditor to GDNativeLibrarySingletonEditor
2017-12-15 22:35:16 +08:00
gdn_env.add_source_files(env.modules_sources, "gdnative_library_singleton_editor.cpp")
gdn_env.add_source_files(env.modules_sources, "gdnative_library_editor_plugin.cpp")
merged gdnative and nativescript module
2017-09-03 18:40:41 +08:00
gdn_env.Append(CPPPATH=['#modules/gdnative/include/'])
added dlscript module This module was written by bojidar-bg and me, with the help of ClikCode and touilleMan. This adds a module to Godot that enables the use of dynamic libraries as a source for scripts. That also allows third party libraries to be linked to Godot more easily and without creating modules. For a readme see https://github.com/GodotNativeTools/godot_headers/blob/master/README.md
2017-04-03 22:11:38 +08:00
Add [Packet/Stream/Multiplayer]PeerGDNative They provide an interface to implement PacketPeer, StreamPeer, and NetworkedMultiplayerPeer via GDNative.
2018-06-27 02:26:51 +08:00
SConscript("net/SCsub")
[GDNative] rename nativearvr extension to arvr
2017-11-10 19:36:50 +08:00
SConscript("arvr/SCsub")
[GDnative] add pluginscript \o/
2017-10-09 05:47:38 +08:00
SConscript("pluginscript/SCsub")
Redoing the ARVR GDNative interface as module and tighter implementation
2017-10-07 21:51:17 +08: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-18 06:23:55 +08:00
from platform_methods import run_in_subprocess
import gdnative_builders
[GDnative] replace gdnative_api_struct.h by a json-based autogenerated system
2017-10-03 11:23:05 +08:00
add NoCache wrapper to Command
2018-06-21 12:33:25 +08:00
_, gensource = gdn_env.CommandNoCache(['include/gdnative_api_struct.gen.h', 'gdnative_api_struct.gen.cpp'],
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-18 06:23:55 +08:00
'gdnative_api.json', run_in_subprocess(gdnative_builders.build_gdnative_api_struct))
[GDnative] replace gdnative_api_struct.h by a json-based autogenerated system
2017-10-03 11:23:05 +08:00
gdn_env.add_source_files(env.modules_sources, [gensource])
[GDNative/NativeScript] fix -rdynamic and removed _init call The _init call was buggy anyway and in the end shouldn't be a thing that's called via ClassDB, it should be something that's language specific, so we leave this out for the bindings. In the commit 66a7763 the SCsub file for GDNative was changed to use a cloned environment, that bricked -rdynamic which needs to be passed down to the linker, which didn't happen with the new env.
2017-08-02 20:21:12 +08:00
env.use_ptrcall = True
[GDNative] added API struct wrapper generator Previously functions of the GDNative API were accessed by letting the loader at load-time resolve the symbols. This causes troubles on Windows (...sigh...), so now the GDNative API isn't exported anymore. This means, that a library that wants to call a GDNative function needs to access it via a struct of pointers that's passed to it at right after the library was loaded. To make the usage easier, those function pointers in the struct can be wrapped in actual function in the global scope. This commit adds a generator for that wrapper code.
2017-10-04 05:07:29 +08:00
if ARGUMENTS.get('gdnative_wrapper', False):
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-18 06:23:55 +08:00
gensource, = gdn_env.CommandNoCache('gdnative_wrapper_code.gen.cpp', 'gdnative_api.json', run_in_subprocess(gdnative_builders.build_gdnative_wrapper_code))
[GDNative] added API struct wrapper generator Previously functions of the GDNative API were accessed by letting the loader at load-time resolve the symbols. This causes troubles on Windows (...sigh...), so now the GDNative API isn't exported anymore. This means, that a library that wants to call a GDNative function needs to access it via a struct of pointers that's passed to it at right after the library was loaded. To make the usage easier, those function pointers in the struct can be wrapped in actual function in the global scope. This commit adds a generator for that wrapper code.
2017-10-04 05:07:29 +08:00
gd_wrapper_env = env.Clone()
gd_wrapper_env.Append(CPPPATH=['#modules/gdnative/include/'])
Disable lto for gdnative wrapper
2018-01-05 02:42:02 +08:00
if gd_wrapper_env['use_lto']:
if not env.msvc:
Fix lto builds on clang compilers The --no-lto option only works on GCC compilers. This breaks LTO builds on MacOS and iPhone when building the gdnative wrappers. -fno-lto works on both brands of compilers.
2018-04-30 18:59:08 +08:00
gd_wrapper_env.Append(CCFLAGS=['-fno-lto'])
gd_wrapper_env.Append(LINKFLAGS=['-fno-lto'])
Disable lto for gdnative wrapper
2018-01-05 02:42:02 +08:00
else:
gd_wrapper_env.Append(CCFLAGS=['/GL-'])
gd_wrapper_env.Append(LINKFLAGS=['/LTCG:OFF'])
[GDNative] disable -fPIC flag with msvc compiler
2017-11-26 03:26:42 +08:00
if not env.msvc:
gd_wrapper_env.Append(CCFLAGS=['-fPIC'])
[GDNative] added API struct wrapper generator Previously functions of the GDNative API were accessed by letting the loader at load-time resolve the symbols. This causes troubles on Windows (...sigh...), so now the GDNative API isn't exported anymore. This means, that a library that wants to call a GDNative function needs to access it via a struct of pointers that's passed to it at right after the library was loaded. To make the usage easier, those function pointers in the struct can be wrapped in actual function in the global scope. This commit adds a generator for that wrapper code.
2017-10-04 05:07:29 +08:00
disable caching for targets using helper functions
2017-11-29 04:27:57 +08:00
lib = gd_wrapper_env.add_library("#bin/gdnative_wrapper_code", [gensource])
Reference in New Issue Copy Permalink