Guidance on Windows build
Hello, I'd like guidance on the Windows qt5 builds. In !241 (merged) I added libraries wcslib-devel libXISF-devel libnova-devel erfa-devel indi-devel cfitsio-devel
provided by Tumbleweed repositories to the suse-qt515
CI image.
Here is an example of the Windows build running on the education/kstars
repository: https://invent.kde.org/education/kstars/-/jobs/1589595
If I understand the methodology well, I'd need to provide the mingw
flavor of those libraries. Looking at how Binary Factory works, there are also dependencies such as libs/indi
or libs/indi_3rdparty
that I could include as well at some point when ready (they are not supported on this OS right now), but I don't see where they are coming from. Other Binary Factory builds?
I see the Craft library list uses libs/*
entries similar to suse-qt515
, but I don't understand where this path is managed now and what is needed there to provide the libraries KStars require.
Reading through Binary Factory logs, I see that https://files.kde.org/craft/prebuilt/packages/22.11/manifest.json has several tools available, but that's not the source of those dependencies. There are also some entries in https://invent.kde.org/sysadmin/ci-utilities/-/tree/master/craft?ref_type=heads, but I can't read their meaning.
How do I know if wcslib
, libXISF
, libnova
, erfa
and cfitsio
are available under libs/
for Windows builds? I suppose I could just add them and...test?