Automated Build

[ctlcltd]

I have set up GitHub Actions to get automated build.

The current setup:

• MSYS2 win64 on windows-2022, latest qt6-base curl
• MSYS2 win32 on windows-2022, latest qt5-base curl
• MacPorts macos-silicon (testing release) on macos-14, latest qt6-qtbase curl
• MacPorts macos-intel on macos-12, latest qt6-qtbase curl
• Miniconda [Miniforge3, conda-forge pkgs] linux AppImage on ubuntu-22.04, latest qt6-main curl
• Aptitude linux AppImage, for cli build, on ubuntu-22.04

Need stable and recent versions of Qt 6, Qt 5 and libcurl4, pre-distributed and trusted binaries.

Need to get the same versions of Qt and libcurl4 on all platforms.

• ubuntu-22.04 comes with qt-6.4.x and curl-7.81
• macos-14 setup could not be backward-compatibile with macOS 13

I tried also:

• ✅ Homebrew linux-appimage on ubuntu-22.04, GLIBC-2.35 built-in
• ❌ Homebrew linux-appimage on ubuntu-20.04, GLIBC-2.35 Homebrew, fails on linking
• ❌ Nix linux-appimage on ubuntu-22.04, GLIBC-2.38 GLIBC-2.36 Nix, fails on linking

I created scripts to automatically resolve and link dependencies, all the libraries that will be bundled with the software, e2se/deployqtwin and e2se/deployqtmacx.

The software distributed for Windows and macOS is not signed, nor distributed through the main distribution channels.

It might be interesting to distribute the software on other channels, example Chocolatey.

Bringing reliable developers into the team, with the ability to sign, could make possible to sign the software and build and test it on Arm64 architectures, for example: Silicon, linux-aarch64 AppImage, win-arm64.

There is a repo e2se/test-workflows to experimenting with build automation.

Ideas, suggestions would be appreciated