lindomarc / tes3mp-forge

A container to simplify the packaging of TES3MP for GNU/Linux

TES3MP-forge

A container to simplify the packaging of TES3MP for GNU/Linux

This Docker image creates a Debian Jessie build environment, compiles a bunch of dependencies with parameters as such to make the resulting TES3MP GNU/Linux package work on most distros and finally summons TES3MP-deploy to build and package TES3MP automatically.

ARM version

Docker Hub

https://hub.docker.com/r/grimkriegor/tes3mp-forge/

Getting the image

Pulling from Docker Hub

docker pull grimkriegor/tes3mp-forge

Building from source

git clone https://github.com/GrimKriegor/TES3MP-forge.git
cd TES3MP-forge
docker build --tag grimkriegor/tes3mp-forge --build-arg BUILD_THREADS=<build-threads> .

Running

docker run --rm -it -v <output-directory>:/build grimkriegor/tes3mp-forge [TES3MP-deploy arguments]

Replace with the path of the directory you want to build TES3MP on. The package will also be there.

By default TES3MP-forge runs TES3MP-deploy with --script-upgrade --cmake-local --skip-pkgs which tells it to check for script upgrades via git, automatically update, and use the build dependencies bundled with this image.

If no parameter is specified on Docker run or start, the default behaviour is to install and package TES3MP.

Tips

Might be a good idea to get a fresh copy of libstdc++.so.6 from a recent system and drop it into the package lib/ directory for increased compatibility with older systems

You can either inject it directly into the .tar.gz package or put it into extra/lib/ and have it be included on all future package builds

mkdir -p <output-directory>/extra/lib
cp -r --preserve=links /usr/lib/libstdc++.so.6* <output-directory>/extra/lib/

The same can be done with the version file, when you are building from hotfix commits but want to keep it compatible with the servers.

mkdir -p <output-directory>/extra/resources/
cp version <output-directory>/extra/resources/