-
-
Notifications
You must be signed in to change notification settings - Fork 74
Closed
Description
#72 is merged and I've decided to give a try at compiling the engine this way. Also note that #12 has some advanced information as well (for those not familiar with podman
or container technology in general). This is a summary of discussion at Godot Contributors chat.
I've managed to build images and managed to build something, but stumbled upon various errors in the process on a clear installation of Fedora 33 (which also made mono crash on Windows).
- First thing first, do not attempt to use
sudo
, aspodman
is designed to work in rootless mode. Otherwise this may lead to permission errors once you build with user (for instance, failing to write tologs
withtee
may prevent other builds from being run at all). - Had to
dnf install patch
manually. - A lot of build steps resulted in permission errors with SELinux enforced. At first I added the
:z
tag to each-v
path argument inbuild.sh
, but it didn't resolve all permission errors, and even crashed in some cases (around building Windows).- Using
sudo setenforce 0
allows to circumvent this before building.
- Using
- Also installed
dnf install wine
on the host to be sure, may be required. - Note sure if
mono
runtime should be installed on the host as well, as resulted inmono: command not found
in some cases. - Errors like
err:seh:install_bpf Unexpected status 0xffffffff, errno 1.
- seems to be innocent.
- Compilation error for macOS: Build experience and issues on Fedora 33 and SELinux #74 (comment).
- Build issues with UWP: Build experience and issues on Fedora 33 and SELinux #74 (comment).
Worth documenting that export REGISTRY="localhost"
must be written in build script if building locally.
Feel free to close this at some point, I'd just like to document the limitations so I can refer to them in case I forget, and may be useful for other newbies like me.
Metadata
Metadata
Assignees
Labels
No labels