Re: [Flightgear-devel] CI update

[Rhys A. <rhy...@gm...>]

Hey James,

Just tried the latest artifact from next (macos) and it seems the
notarization hasn't worked properly - Job log shows it failed because it
was missing -i (issuer), error is line 158 if you wanted to jump to it
quickly. Still does not open straight away, as apple can't scan it for
malware... (See screenshot: https://prnt.sc/dflZJWrboOnZ) Running Sonoma
14.3.1

Also looks like the FG icon is not showing, its missing from
flightgear.app/contents/resources where it used to live.

Rhys


On Thu, 24 Oct 2024 at 11:36, James Turner <ja...@fl...> wrote:

> Hey folks, a status update on the GitLab CI:
>
> - nightly builds are working for all three platforms. The artefacts are
> temporarily only available by digging into the GitLab UI, we will expose a
> link to them on the Pages website that Gijs is working on. But unlike
> Jenkins, it’s fine to download from GitLab, but please DO NOT  document the
> currently location on the Wiki or forum; they are still subject to
> evolution:
>
> https://gitlab.com/flightgear/fgmeta/-/artifacts
>
> Notably this link mixes nightly and release builds : again it’s fine if
> you know what you are doing, but do not point end users at this page :
> patience is required :)
>
> (We will make a stable Page where the latest successful nightly build is
> available, and then we can document that - still ToBeDone)
>
> - the Linux night built uses the most recent ‘linuxdeployqt’ based on
> Ubuntu Focal - which is not that recent. Brendan is working on updating to
> use the replacement ‘linuxdeploy’ tool but I’ll leave that to him. (2024.1
> will use linuxdeployqt for its lifetime, is my expectation)
>
> - the macOS build should have full notarization and code-signing (so no
> Gatekeeper warnings). However, it's unclear to me what our minimum system
> version requirements are, because it will be a weird mixture of the lowest
> version we specify (10.15), the XCode toolchain on the CI machines, and the
> version Qt was built with. If your system is too old, please let me know,
> but you might be out of luck because my hands are tied by the compilers /
> toolchains / dependencies here. For example we’re depending on Apple
> shipping liblzma in /usr/lib, but I can’t find the lowest version at which
> they started including it….
>
> (10.15 is my *guess* of our practical min system version, but I don’t have
> a system anywhere near that old to test against, nor do I wish to find
> one……)
>
> But the good news is, the macOS built is fat, Apple Silicon users rejoice.
>
> (All this will also apply to 2024.1 on macOS)
>
> - the Windows installer seems to be working fine. As previously, we
> currently have *no* code-signing so we get a lot of angry warnings from
> Windows but I believe I have found a suitable code-signing solution:
>
> https://shop.certum.eu/open-source-code-signing-on-simplysign.html
>
> … but this is still TBD in the coming weeks - hopefully ready for 2024.1.1
>
> - On Windows and macOS we’re now using Qt 6.7 which is considerably more
> recent, and will change how the launcher renderers (because Qt 6 prefers
> Metal / D3D over OpenGL, for its own rendering - OSG should be unaffected).
> This should be ‘completely unnoticeable’ in practice but lets see.
>
> In general it’s worth trying these builds on whatever platforms you wish:
> knowing that they install + run correctly would be good. If you encounter
> problems, please be clear which date you grabbed the build since things are
> changing fast. Most of it applies to the pending 2024.1 release so the more
> confidence we have that it will work for as many people as possible, the
> better.
>
> Kind regards,
> James
>
> _______________________________________________
> Flightgear-devel mailing list
> Fli...@li...
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>