Fixed compiling on Windows
Make crash dump printing work better on Windows
Tweaked Breakpad build
Fixed Breakpad build for Godot 4
Switched to WINDOWS_ENABLED
Removed some non buildable files listed in the files to build
Ran clang format
Fixed the other formatting issues detected by CI
Removed a comment and added clarifying comment on crash dump message
as to why it is printed twice on Windows
Make an ugly string conversion to make Windows build work
Tweaked the build configuration and formatted again
removed lss
Add lss properly
Reinitialize breakpad after mono initialization on Linux
otherwise the breakpad signal handlers are not active
Disable Windows crash handler on destruction similarly to Linux
Renamed breakpad_enabled to use_breakpad
Forgot to wrap one piece of code inside ifdef USE_BREAKPAD
Updated copyright years in the added files
Fix register types for breakpad
Fixed dir access
Removed musl and elf_reader
which was the only thing seemingly depending on it
Updated header guards
Removed the memdelete call
Adds "--accurate-breadcrumbs" CLI command
Additionally, leave out breadcrumbs code in non-debug, non-dev builds.
Fix regression introduced in #98388 where command_insert_breadcrumb() is
called even in non-debug builds.
Fixes#98338
`core/os/os.h` doesn't use `core/io/image.h`. It just brings
transitive dependencies. Lots of dependencies because `core/os/os.h`
is transitively included in almost every file of godot
Also added `core/io/image.h` into files^1 where `Ref<Image>` and `core/os/os.h`
were used to prevent obscure errors involving `Ref<Image>`
^1 except those which include `core/io/image_loader.h` or `core/io/image.h` by
corresponding .h file with the same name
Signed-off-by: Yevhen Babiichuk (DustDFG) <dfgdust@gmail.com>
Co-authored-by: A Thousand Ships <96648715+AThousandShips@users.noreply.github.com>
XR is disabled when 3D is disbled so there is no sense in
setting xr specific settings and adding `--xr-mode` option
Signed-off-by: Yevhen Babiichuk (DustDFG) <dfgdust@gmail.com>
If the module is enabled (default), 2D physics works as it did before.
If the module is disabled and no other 2D physics server is registered
(via a module or GDExtension), then we fall back to a dummy
implementation which effectively disables 2D physics functionality (and
a warning is printed).
The dummy 2D physics server can also be selected explicitly, in which
case no warning is printed.
If the module is enabled (default), 3D physics works as it did before.
If the module is disabled and no other 3D physics server is registered
(via a module or GDExtension), then we fall back to a dummy
implementation which effectively disables 3D physics functionality (and
a warning is printed).
The dummy 3D physics server can also be selected explicitly, in which
case no warning is printed.