[OSG] Update commit to e568aace1e62de021df9955c62429cbe55516fd3
openmw-deps-build
This is a repository to host CI jobs to build dependencies for OpenMW via vcpkg to be cached as binary artifacts at https://gitlab.com/OpenMW/openmw-deps. Dependencies are pushed to openmw-deps on release.
Local Dependency Installation
Vcpkg has system requirements.
Core Commands
- Install:
vcpkg install --overlay-ports=ports --overlay-triplets=triplets --triplet TRIPLET --host-triplet HOST_TRIPLET (usually the same as TRIPLET) - Export:
vcpkg export --x-all-installed --raw --output OUTPUT_DIRECTORY_NAME --output-dir DIRECTORY_TO_OUTPUT_INTO
Linux
In CI, we build using almalinux for maximum distro compatibility. If you are not on almalinux, you can run the commands that are done in the ./.github/workflows/build.yaml under the linux matrix in a Dockerfile or distrobox that pulls from almalinux:9 and then install vcpkg and the dependencies listed in the CI and then proceed with the core vcpkg commands with the x64-linux-dynamic triplet.
There's also a Docker Compose container definition in docker/generic-linux-deps that should run the setup commands for you.
There's a readme in that directory explaining what to do.
MacOS
You need to install the following: brew install autoconf autoconf-archive automake
vcpkg install --overlay-ports=ports --overlay-triplets=triplets --triplet arm64-osx-dynamic --host-triplet arm64-osx-dynamicvcpkg export --x-all-installed --raw --output vcpkg-macos-test --output-dir DIRECTORY
Windows
Running the core commands should work out of the box on a Windows machine of the matching architecture.
Testing Dependencies with OpenMW Locally
MacOS
You will need to change the variables towards the top of the OpenMW before_script.macos.sh file to:
DEPENDENCIES_ROOT_PATH="/DIRECTORY/vcpkg-macos-test"
And then proceed as normal.
Linux
TBD
Secret Setup in CI for E2E Testing
This is so the built dependencies show up in your fork of https://gitlab.com/OpenMW/openmw-deps.
You can test the repo is working on your own fork using a deploy key and a gpg key you generate.
To make this work properly multiple secrets have to be configured:
SSH_PRIVATE_KEYwith private SSH key allowed to push changes to repository specified viaPUSH_URLvariable (e.g. generated byssh-keygen).- You should use a deploy key setup on your fork of https://gitlab.com/OpenMW/openmw-dep
GPG_PRIVATE_KEYwith private GPG key to sign commits with GPG signature (e.g. generated withgpg --full-generate-key).GPG_PRIVATE_KEY_PASSPHRASEa passphrase for theGPG_PRIVATE_KEYto make it possible to use the GPG key (e.g. the value used duringgpg --full-generate-key).- You must generate a gpg key with the git author information used in CI, i.e.
[email protected]. It does not need to be associated with any account.
- You must generate a gpg key with the git author information used in CI, i.e.
Also the following variable has to be set:
PUSH_URLwith target SSH-based URL forgit pushcommand (e.g.[email protected]:OpenMW/openmw-deps.gitor your fork).
Any pushes should create a branch/commit on the openmw-dep repo. However, the manifest file links will not work in your fork of openmw-deps. You will need to create a tag/release for that to work.