62477d8c65
- for now all versions start with v6.0
- CICD builds use the monolithic build number as patch level, e.g. v6.0.12345
- local builds use the following algorithm
- find the newest commit with a CICD build number that is included in the
working tree
- count the number of commits in the working tree since that commit
- if there are no commits since the last CICD build, the local build version
will be v6.0.12345-local
- if there are N commits since the last CICD build, it will be
v6.0.12345-N-local
- test builds in the CICD that don't create artifacts simply use a dummy release
in order to not incorrectly increment the build number and also not to waste
time and resources by manually checking out the nightly-build repo for each of
these builds.
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Creating a Windows installer
The scripts here help with cross building Subsurface and smtk2ssrf for Windows.
The preferred method to create a Windows installer is to use our own docker image that has all the build components pre-assembled. All it takes is this:
cd /some/path/windows
git clone https://github.com/subsurface/subsurface
cd subsurface
git submodule init
git submodule update
docker run -v /some/path/windows:/__w subsurface/mxe-build-container:2.2 /bin/bash /__w/subsurface/packaging/windows/create-win-installer.sh
This will result in subsurface-VERSION.exe and smtk2ssrf-VERSION.exe to be created.