public_mirrors
/
build-containers
mirror of https://github.com/godotengine/build-containers.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
build-containers/Dockerfile.windows

41 lines
2.1 KiB
Docker
Raw Normal View History

Properly pass img_version to all containers Continuation and fixup of #23.
2019-12-02 13:30:41 +01:00
ARG img_version
FROM godot-mono:${img_version}
Initial commit
2019-01-07 21:51:22 +01:00
ARG mono_version
Mono: Allow specifying fixed git hash and pretty image version Specifying only a branch like '2019-08' is problematic if upstream commits something between the builds of two containers. We could make a tarball in the first container build and reuse that, but we need the flexibility of Git for some patching in the Android and JavaScript builds, so instead we allow specifying a git tree-ish as the third argument. We can therefore also give a pretty version string to use for the image name as second argument, e.g. 6.6.0.160 for bef1e6335812d32f8eab648c0228fc624b9f8357. As we can't `git clone` a commit hash directly, we still need to provide both branch name and then commit hash for this use case.
2019-12-03 12:47:51 +01:00
ARG mono_commit
Initial commit
2019-01-07 21:51:22 +01:00
Use git tag to checkout stable mono releases The main reason is that upstream Mono tends to miss some important files in its tarballs, so Git tags appears to be a more reliable medium. Also group RUN commands to reduce the number of intermediate dependencies.
2019-11-15 10:49:02 +01:00
RUN if [ -z "${mono_version}" ]; then echo -e "\n\nargument mono-version is mandatory!\n\n"; exit 1; fi && \
dnf -y install --setopt=install_weak_deps=False \
Windows: Workaround Mono 6 BCL cross-compiling bug using Wine This can be reverted once a proper fix has been deployed in upstream Mono. No ETA yet as we're busy and it's unlikely to happen if we don't do it ourselves :) Co-authored-by: Hein-Pieter van Braam-Stewart <hp@tmm.cx>
2019-12-16 12:53:38 +01:00
mingw32-gcc mingw32-gcc-c++ mingw32-winpthreads-static mingw64-gcc mingw64-gcc-c++ mingw64-winpthreads-static yasm wine && \
dnf clean all && \
git clone https://github.com/mono/mono --branch ${mono_version} --single-branch && \
Mono: Allow specifying fixed git hash and pretty image version Specifying only a branch like '2019-08' is problematic if upstream commits something between the builds of two containers. We could make a tarball in the first container build and reuse that, but we need the flexibility of Git for some patching in the Android and JavaScript builds, so instead we allow specifying a git tree-ish as the third argument. We can therefore also give a pretty version string to use for the image name as second argument, e.g. 6.6.0.160 for bef1e6335812d32f8eab648c0228fc624b9f8357. As we can't `git clone` a commit hash directly, we still need to provide both branch name and then commit hash for this use case.
2019-12-03 12:47:51 +01:00
cd /root/mono && \
if [ ! -z "${mono_commit}" ]; then git checkout ${mono_commit}; fi && \
git submodule update --init && \
Windows: Workaround Mono 6 BCL cross-compiling bug using Wine This can be reverted once a proper fix has been deployed in upstream Mono. No ETA yet as we're busy and it's unlikely to happen if we don't do it ourselves :) Co-authored-by: Hein-Pieter van Braam-Stewart <hp@tmm.cx>
2019-12-16 12:53:38 +01:00
git apply -3 /root/files/patches/wine-mono.patch && \
export WINE_BITS=64 && \
bash /root/files/mono-build-win32.sh --prefix=/root/dependencies/mono-64 --host=x86_64-w64-mingw32 && \
Use git tag to checkout stable mono releases The main reason is that upstream Mono tends to miss some important files in its tarballs, so Git tags appears to be a more reliable medium. Also group RUN commands to reduce the number of intermediate dependencies.
2019-11-15 10:49:02 +01:00
git clean -fdx && \
Initial commit
2019-01-07 21:51:22 +01:00
cp /root/dependencies/mono-64/bin/libMonoPosixHelper.dll /root/dependencies/mono-64/bin/MonoPosixHelper.dll && \
rm -f /root/dependencies/mono-64/bin/mono /root/dependencies/mono-64/bin/mono-sgen && \
ln -s /usr/bin/mono /root/dependencies/mono-64/bin/mono && \
ln -s /usr/bin/mono-sgen /root/dependencies/mono-64/bin/mono-sgen && \
Windows: Prevent 32-bit build failure from skipping symlinks Like most programming language, in a logic statement `A && B || C`, bash will not evaluate B if A is false (failing in our case). Using `A && (B || C)` to prevent that. A build error in the Windows 32-bit Mono build thus caused skipping all subsequent `ln` statements up until `|| /bin/true`, which is used to link only the folders which are missing from the self-built mono prefix. The build error still needs to be fixed but it doesn't seem to prevent using the resulting container to build 32-bit Windows binaries.
2020-01-07 09:54:29 +01:00
(ln -sf /usr/lib/mono/* /root/dependencies/mono-64/lib/mono/ || /bin/true) && \
Use git tag to checkout stable mono releases The main reason is that upstream Mono tends to miss some important files in its tarballs, so Git tags appears to be a more reliable medium. Also group RUN commands to reduce the number of intermediate dependencies.
2019-11-15 10:49:02 +01:00
cp -rvp /etc/mono /root/dependencies/mono-64/etc && \
Windows: Workaround Mono 6 BCL cross-compiling bug using Wine This can be reverted once a proper fix has been deployed in upstream Mono. No ETA yet as we're busy and it's unlikely to happen if we don't do it ourselves :) Co-authored-by: Hein-Pieter van Braam-Stewart <hp@tmm.cx>
2019-12-16 12:53:38 +01:00
export WINE_BITS=32 && \
Windows: Prevent 32-bit build failure from skipping symlinks Like most programming language, in a logic statement `A && B || C`, bash will not evaluate B if A is false (failing in our case). Using `A && (B || C)` to prevent that. A build error in the Windows 32-bit Mono build thus caused skipping all subsequent `ln` statements up until `|| /bin/true`, which is used to link only the folders which are missing from the self-built mono prefix. The build error still needs to be fixed but it doesn't seem to prevent using the resulting container to build 32-bit Windows binaries.
2020-01-07 09:54:29 +01:00
(bash /root/files/mono-build-win32.sh --prefix=/root/dependencies/mono-32 --host=i686-w64-mingw32 || /bin/true) && \
Mono: Allow specifying fixed git hash and pretty image version Specifying only a branch like '2019-08' is problematic if upstream commits something between the builds of two containers. We could make a tarball in the first container build and reuse that, but we need the flexibility of Git for some patching in the Android and JavaScript builds, so instead we allow specifying a git tree-ish as the third argument. We can therefore also give a pretty version string to use for the image name as second argument, e.g. 6.6.0.160 for bef1e6335812d32f8eab648c0228fc624b9f8357. As we can't `git clone` a commit hash directly, we still need to provide both branch name and then commit hash for this use case.
2019-12-03 12:47:51 +01:00
cd /root && \
Initial commit
2019-01-07 21:51:22 +01:00
cp /root/dependencies/mono-32/bin/libMonoPosixHelper.dll /root/dependencies/mono-32/bin/MonoPosixHelper.dll && \
rm -f /root/dependencies/mono-32/bin/mono /root/dependencies/mono-32/bin/mono-sgen && \
ln -s /usr/bin/mono /root/dependencies/mono-32/bin/mono && \
ln -s /usr/bin/mono-sgen /root/dependencies/mono-32/bin/mono-sgen && \
Windows: Prevent 32-bit build failure from skipping symlinks Like most programming language, in a logic statement `A && B || C`, bash will not evaluate B if A is false (failing in our case). Using `A && (B || C)` to prevent that. A build error in the Windows 32-bit Mono build thus caused skipping all subsequent `ln` statements up until `|| /bin/true`, which is used to link only the folders which are missing from the self-built mono prefix. The build error still needs to be fixed but it doesn't seem to prevent using the resulting container to build 32-bit Windows binaries.
2020-01-07 09:54:29 +01:00
(ln -sf /usr/lib/mono/* /root/dependencies/mono-32/lib/mono/ || /bin/true) && \
Use git tag to checkout stable mono releases The main reason is that upstream Mono tends to miss some important files in its tarballs, so Git tags appears to be a more reliable medium. Also group RUN commands to reduce the number of intermediate dependencies.
2019-11-15 10:49:02 +01:00
cp -rvp /etc/mono /root/dependencies/mono-32/etc && \
Windows: Workaround Mono 6 BCL cross-compiling bug using Wine This can be reverted once a proper fix has been deployed in upstream Mono. No ETA yet as we're busy and it's unlikely to happen if we don't do it ourselves :) Co-authored-by: Hein-Pieter van Braam-Stewart <hp@tmm.cx>
2019-12-16 12:53:38 +01:00
rm -rf /root/mono && \
dnf -y remove wine
Initial commit
2019-01-07 21:51:22 +01:00
Several small fixes * Mono config on MacOSX is not portable from the Linux and Windows version. * Rename the compilers so that 'gcc' and 'g++' are the new version by default. * Add default environment variables to containers.
2019-01-17 23:06:38 +01:00
ENV MONO32_PREFIX=/root/dependencies/mono-32
ENV MONO64_PREFIX=/root/dependencies/mono-64
Use /bin/bash as default CMD instruction The previous `['/bin/bash']` was not working, running the image with `podman run -it <name>` would evaluate to: ``` > sh -c ['/bin/bash'] sh: [/bin/bash]: No such file or directory ```
2019-11-15 11:22:07 +01:00
CMD /bin/bash