-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create documentation for building a Godot fork #44
Comments
The way you compile without sanitizers is by just... not enabling sanitizers. Docs: https://github.com/the-mirror-gdp/godot?tab=readme-ov-file#compiling-from-source |
Thank you for your comment, I think when the time comes, since this Issue is not a high priority, this information would be better described in The Mirror's documentation. |
I found the information I was looking for, these repositories have everything you need to create release builds. Build scripts used for official Godot Engine. Godot engine build containers. Godot's buildroot soft-fork for generating toolchains to make portable Linux releases of Godot games. |
Thanks @aaronfranke and @VladimirLevadnij, I'll close this then. |
I'm creating an issue in this repository because this repository is an issue hub, but this issue concerns a Godot fork in a child repository https://github.com/the-mirror-gdp/godot
Since the Godot fork with expanded functionality is an important component of The Mirror project, it is necessary to place instructions in the official documentation in the "Open-Source Code" section for assembling working editor applications based on this Godot fork, at least for the main platforms Windows, macOS and Linux.
https://docs.themirror.space/docs/category/open-source-code
Currently there is a problem with using GitHub Actions for building, this is written in the issue the-mirror-gdp/godot#2
While building using GitHub Actions does not work, you can write the build process using SCons in the documentation.
Respected @aaronfranke on Discord commented:
It turns out that the first step in the documentation is to describe how to build without sanitizers, additionally indicating in the documentation the reason why sanitizers are not currently used, so that users of the documentation do not have unnecessary questions.
The text was updated successfully, but these errors were encountered: