a753845d5a
- use hidapi grantlee and mdbtools from MXE - update MXE version to use QT 5.15, and pull in libzstd and CMake 3.17.3 - fix linking of winmm on windows build with new mxe - add some instructions on building the container - add some new dependancies from QT 5.15 to the packaging - add a patch to MXE to Build qtconnectivity with native-win32-bluetooth [Dirk Hohndel: small refactor] Signed-off-by: Paul Buxton <paulbuxton.mail@googlemail.com> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
1.9 KiB
Instructions for building the container environment and using it to build/package subsurface.
This document assumes you have alreay installed docker and have checked out subsurface according to the instructions in the INSTALL document.
If you are just wantint to build with the current mxe build container then starting from the folder above subsurface run
docker run -v $PWD/win32:/win/win32 -v $PWD/subsurface:/win/subsurface --name=mybuilder -w /win -d subsurface/mxe-build-container:1.x /bin/sleep 60m
replacing the x in the mxe-build-container tag with the current version e.g.
docker run -v $PWD/win32:/win/win32 -v $PWD/subsurface:/win/subsurface --name=mybuilder -w /win -d subsurface/mxe-build-container:1.0 /bin/sleep 60m
Next you need to prep the container by installing some prerequisites
docker exec -t mybuilder bash subsurface/.github/workflows/scripts/windows-container-prep.sh 2>&1 | tee pre-build.log
Finaly the actual build is done with
docker exec -t mybuilder bash subsurface/.github/workflows/scripts/windows-in-container-build.sh 2>&1 | tee build.log
To get the built binary out of the container
docker exec -t mybuilder bash cp /subsurface-installer.exe /win/win32
Which will copy the installer into the win32 folder which will be a sibling of the subsurface folder.
Modifying the container
If you want to make changes to the build environment used in the conatiner The script scripts/docker/mxe-build-container.sh will build the Docker image itself. The sha of the version of MXE we are using is built into this, so you can update that to whatever version is required, and modify dockerfiles and settings-stage1.mk and settings-stage2.mk to pull in any other prerequisites as required.
If you are working on updating the container then you should incrment the minor version of the variable VERSION in the script as otherwise it will clash with the version used in production