Dear Craft Team, Thank you for your support of the KStars project over the years. We have encountered a bug in craft that affects the packaging of KStars. It has not been a problem before as we were just building for MacOS on x86_64 and users would just run KStars in rosetta in the past. But we have been working hard over the last few months to update KStars to QT6 and to natively build in arm64 apple silicon, and it was during this work that we encountered the bug. As of now, this bug affects two of our INDI 3rd Party Camera driver libraries that need to be provided with KStars for users to use for astrophotography. In the future, it will likely affect more as we move toward natively supporting apple silicon. These camera driver libraries have been generously provided by the camera manufacturers so that INDI and KStars can control their cameras. The issue is that these driver libraries are universal MacOS binaries containing both the x86_64 version and the arm64 version. We are able to build and use KStars just fine in craft for both x86 and arm64, those functions of craft are working great. The issue right now is just with packaging.
Here is an example of the failure: https://invent.kde.org/education/kstars/-/jobs/3062039 As far as I can tell the issue is that the Mac Packager on this line 228 expects otool -D to return just one line, the install name of the library: https://invent.kde.org/packaging/craft/-/blob/master/bin/Packager/MacBasePackager.py?ref_type=heads#L228 But since these libraries are universal binaries, they return two lines, the install names for each architecture. Would you please help us to allow the craft packager to handle universal binaries on MacOS? Thanks, Rob Lancaster
