mirror of
https://github.com/godotengine/godot
synced 2024-09-05 20:59:56 +00:00
39facb35a0
Implements https://github.com/godotengine/godot-proposals/issues/3371. New `target` presets ==================== The `tools` option is removed and `target` changes to use three new presets, which match the builds users are familiar with. These targets control the default optimization level and enable editor-specific and debugging code: - `editor`: Replaces `tools=yes target=release_debug`. * Defines: `TOOLS_ENABLED`, `DEBUG_ENABLED`, `-O2`/`/O2` - `template_debug`: Replaces `tools=no target=release_debug`. * Defines: `DEBUG_ENABLED`, `-O2`/`/O2` - `template_release`: Replaces `tools=no target=release`. * Defines: `-O3`/`/O2` New `dev_build` option ====================== The previous `target=debug` is now replaced by a separate `dev_build=yes` option, which can be used in combination with either of the three targets, and changes the following: - `dev_build`: Defines `DEV_ENABLED`, disables optimization (`-O0`/`/0d`), enables generating debug symbols, does not define `NDEBUG` so `assert()` works in thirdparty libraries, adds a `.dev` suffix to the binary name. Note: Unlike previously, `dev_build` defaults to off so that users who compile Godot from source get an optimized and small build by default. Engine contributors should now set `dev_build=yes` in their build scripts or IDE configuration manually. Changed binary names ==================== The name of generated binaries and object files are changed too, to follow this format: `godot.<platform>.<target>[.dev][.double].<arch>[.<extra_suffix>][.<ext>]` For example: - `godot.linuxbsd.editor.dev.arm64` - `godot.windows.template_release.double.x86_64.mono.exe` Be sure to update your links/scripts/IDE config accordingly. More flexible `optimize` and `debug_symbols` options ==================================================== The optimization level and whether to generate debug symbols can be further specified with the `optimize` and `debug_symbols` options. So the default values listed above for the various `target` and `dev_build` combinations are indicative and can be replaced when compiling, e.g.: `scons p=linuxbsd target=template_debug dev_build=yes optimize=debug` will make a "debug" export template with dev-only code enabled, `-Og` optimization level for GCC/Clang, and debug symbols. Perfect for debugging complex crashes at runtime in an exported project. |
||
|---|---|---|
| .. | ||
| doc_classes | ||
| editor | ||
| extensions | ||
| structures | ||
| config.py | ||
| gltf_defines.h | ||
| gltf_document.cpp | ||
| gltf_document.h | ||
| gltf_document_extension.cpp | ||
| gltf_document_extension.h | ||
| gltf_document_extension_convert_importer_mesh.cpp | ||
| gltf_document_extension_convert_importer_mesh.h | ||
| gltf_state.cpp | ||
| gltf_state.h | ||
| gltf_template_convert.h | ||
| README.md | ||
| register_types.cpp | ||
| register_types.h | ||
| SCsub | ||
Godot GLTF import and export module
In a nutshell, the GLTF module works like this:
- The
structures/folder contains GLTF structures, the small pieces that make up a GLTF file, represented as C++ classes. - The
extensions/folder contains GLTF extensions, which are optional features that build on top of the base GLTF spec. GLTFStateholds collections of structures and extensions.GLTFDocumentoperates on GLTFState and its elements.- The
editor/folder uses GLTFDocument to import and export 3D models.