Build instructions update

[Thulium-Drake]

Hi there,

I ran into some issues compiling it in a Podman container as there seems to be a few things missing from the build instructions.

Here's what I did, so far:

• Clone all repos to a folder (in my case ~/git)
• Start a Fedora 42 container in Podman and mount that directory inside it

podman run -it -v ~/git:/root:Z fedora:42 /bin/bash

• Install all dependencies

dnf install -y nasm autoconf automake libtool pkgconf libtool-ltdl-devel ninja-build python3-jinja2 cmake make gcc gcc-c++ curl zip unzip tar git libX11-devel libXft-devel libXext-devel wayland-devel libxkbcommon-devel ibus-devel mesa-libEGL-devel diffutils perl-open perl-FindBin libatomic

• Prepare vcpkg and configure the project (remember, I am running this in a container, so everything is as root, but that's OK)

cd /root/vcpkg
export VCPKG_ROOT=$(pwd)
./bootstrap-vcpkg.sh
export PATH="$PATH:$VCPKG_ROOT"
mkdir /root/CnC_Generals_Zero_Hour/build
cd /root/CnC_Generals_Zero_Hour/build
cmake --preset=default -DVCPKG_INSTALL_OPTIONS="--allow-unsupported" -DSAGE_USE_SDL3=ON ../

• After that's done, enter the default folder and compile the binary

cd /root/CnC_Generals_Zero_Hour/build/default
cmake --build . --config Release

This does result in a folder with the RTS binary in it, but so far I haven't been able to start it on my Fedora system.

[albsen]

I've gone through a similar exercise using docker buildx. The resulting executable is unfortunately currently not working, I will update here when it is. So far I have the following dockerfile and build command:

# syntax=docker/dockerfile:1.4

############################
# 1) Builder stage
############################
FROM fedora:42 AS builder

ENV TRIPLET=x64-linux
ENV VCPKG_ROOT=/work/vcpkg
ENV PATH="$PATH:$VCPKG_ROOT"

# Tools + headers for build
RUN dnf install -y \
  nasm autoconf automake libtool pkgconf libtool-ltdl-devel ninja-build \
  python3-jinja2 cmake make gcc gcc-c++ curl zip unzip tar git diffutils \
  perl-open perl-FindBin libatomic file \
  libX11-devel libXft-devel libXext-devel \
  wayland-devel libxkbcommon-devel mesa-libEGL-devel \
  ibus-devel \
  && dnf clean all

# Copy sources (adjust paths to your repo layout)
WORKDIR /work
COPY vcpkg/ ./vcpkg/
COPY CnC_Generals_Zero_Hour/ ./src/

# Bootstrap vcpkg + install required libs for the d3dx8 compat
RUN cd /work/vcpkg && ./bootstrap-vcpkg.sh && \
  /work/vcpkg/vcpkg install glm:${TRIPLET} gli:${TRIPLET}

# Configure & build (Ninja is single‑config → use CMAKE_BUILD_TYPE=Release)
RUN cmake -S /work/src -B /work/src/build/default \
  -G Ninja \
  -DCMAKE_BUILD_TYPE=Release \
  -DCMAKE_TOOLCHAIN_FILE=/work/vcpkg/scripts/buildsystems/vcpkg.cmake \
  -DVCPKG_TARGET_TRIPLET=${TRIPLET} \
  -DSAGE_USE_GLM=ON \
  -DSAGE_USE_SDL3=ON \
  && cmake --build /work/src/build/default -j"$(nproc)"

############################
# 2) Export stage (just the binary/binaries)
############################
FROM scratch AS export
COPY --from=builder /work/src/build/default/ /out/

and building it via:

DOCKER_BUILDKIT=1 docker buildx build \
  --progress=plain \
  --platform linux/amd64 \
  --output type=local,dest=./artifacts \
  -t cnc-build .

This will create an executable RTS in out/GeneralsMD/Code/,

there are also libraries needed in:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:[FILL_IN_YOUR_OWN]/artifacts/out/_deps/miles-build:[FILL_IN_YOUR_OWN]/artifacts/out/_deps/dxvk-src/lib/        

[Fighter19]

I ran into some issues compiling it in a Podman container as there seems to be a few things missing from the build instructions.

Could you please elaborate as to which things are missing exactly?
podman and Fedora are outside the scope of the README. I can enable a Wiki and pages can be added there.

This does result in a folder with the RTS binary in it, but so far I haven't been able to start it on my Fedora system.

This seems highly unlikely. The current RTS binary segfaults if not run in the folder of the game.
I'm looking to change this in the near future. However it should work when run from the folder.

Information e.g. via gdb would be appreciated if it still fails regardless.