Alexei Kotov b99e0c4ee9 Merge pull request #50 from ssunday/update-openmw-osg
[OSG] Update commit to e568aace1e62de021df9955c62429cbe55516fd3
2026-11-05 22:28:04 +03:00
2026-09-19 01:57:41 +01:00
2026-09-19 01:34:43 +01:00
2026-09-05 23:16:09 +01:00
2024-03-04 00:03:20 +01:00
2026-09-19 01:34:28 +01:00
2024-08-24 01:39:33 +02:00
2026-09-19 01:34:43 +01:00
2026-09-05 23:15:52 +01:00

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

  1. vcpkg install --overlay-ports=ports --overlay-triplets=triplets --triplet arm64-osx-dynamic --host-triplet arm64-osx-dynamic
  2. vcpkg 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_KEY with private SSH key allowed to push changes to repository specified via PUSH_URL variable (e.g. generated by ssh-keygen).
  • GPG_PRIVATE_KEY with private GPG key to sign commits with GPG signature (e.g. generated with gpg --full-generate-key).
  • GPG_PRIVATE_KEY_PASSPHRASE a passphrase for the GPG_PRIVATE_KEY to make it possible to use the GPG key (e.g. the value used during gpg --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.

Also the following variable has to be set:

  • PUSH_URL with target SSH-based URL for git push command (e.g. [email protected]:OpenMW/openmw-deps.git or 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.

S
Description
No description provided
Readme Apache-2.0
260 KiB
0 Stars 1 Watchers 0 Forks
2026-11-05
Latest
2026-11-13 03:46:08 -10:00
Languages
CMake 67.1%
PowerShell 17.4%
Shell 15.5%