Follow-up to https://github.com/godotengine/godot/pull/65094.
Also reverts LTO change from #62, we found that while it's much slower
to link, full LTO still produces smaller binaries and that's quite
important for the Web platform.
The `server` platform has now been replaced by the "headless" `DisplayServer`
which is registered on all desktop platforms.
Disable JavaScript and UWP builds which are not currently supported in 4.0.
We were shipping a pre-built version but it only works on specific distros
as it's tightly coupled to openssl. When upgrading from F34 to F35 it started
segfaulting.
We now rely on the version packaged by Fedora which should be installed on the
host, or compiled and installed manually in PATH by users.
Cf. https://github.com/godotengine/build-containers/pull/84
- Linux builds are now done on Fedora using a custom Godot SDK instead of
relying on an old Ubuntu version for portability.
Removes need for various workarounds.
- macOS Mono builds now include support for Apple Silicon / arm64, both
architectures are concatenated in universal binaries.
This new config is compatible with the `3.x` branch for Godot 3.4.
It might or might not work as is for `master` / Godot 4.0. Porting it will
be the next step.
For other platforms:
- Android is stripped by gradle already.
- HTML5 already has stripped release builds.
Debug builds could be stripped with fastcomp's wasm-strip but it might be
deprecated?
- iOS is a static lib and shouldn't be stripped.
- UWP can't be stripped by default GNU strip it seems.
This allows signing the editor .app (will be done in next commit) and should
let users sign their macOS exports.
Co-authored-by: Shane Liesegang <shane@techie.net>
Classical builds now use Emscripten 2.0.10 and have threads and gdnative
templates.
Mono builds still use Emscripten 1.39.9 for compatibility with Mono 6.12.x, so
they cannot have GDNative support which requires 2.0.10+. And threads build
triggers wasm-ld errors without LTO, and wasm-ld crash with LTO, so no dice
there either.
Co-authored-by: Fabio Alessandrelli <fabio.alessandrelli@gmail.com>
The sums are included both in the release folder, and in a separate
`sha512sums` folder in the base directory, to allow verifying that
the sums on the download repository haven't been tampered with.
The in-container build scripts now get passed CLASSICAL and MONO env
variables which can be used to build one or the other, or both
(default).
`build.sh`, `build-release.sh` and `build-templates.sh` now all expect
command line switches to specify the version details, and optionally
which flavor to build.
For example to build Mono only:
./build.sh -v 3.2-beta4 -g master -b mono
./build-release.sh -v 3.2-beta4 -b mono
./build-templates.sh -v 3.2-beta4 -t 3.2.beta4 -b mono
Also took the opportunity to do some extra cleanup, like removing
unnecessary `builtin_*` options since they all default to True, even
for Linux in 3.2, as well as `use_lto` and `use_static_cpp` options
on platforms which don't implement them.
And I improved the `build-release.sh` script to be a bit easier to
read, and avoid having too many stray folders to cleanup.
The build scripts should now generate the final structure that we'd use
on the official mirrors, with the `mono` distribution as a subfolder of
the main release folder.
