Might be an issue with those using INTEL Macs and Sonoma.
I'm running Sonima on an old 2012 Intel Mac and had to use the above "xattr -cr" remove attributes command.

It still doesn't work 3.7 on my OSX, I had to go back to 3.6.8 stable or my Windows (yuck)

As stated above in Rob's post, version 3.7 only works on macOS 14.x (Sonoma) and likely also only on Macs with -Silicon (M1, M2, M3).

No, Sonoma and version 3.7 also works on Intel hardware, which I have.

Yes, it definitely works on Intel since I built the DMG on an Intel Mac and I use it on one.

Very good then . Well, that was the assumption by someone else in an earlier post.

May I ask again about compiling INDI 3rd party drivers for KStars on macOS? ... Those are typically being compiled for the LINUX version.

In particular, for the AvalonUD mount .

Sure, so originally when I was porting KStars to Mac, I always built the drivers and KStars with home-brew. When we started trying to distribute it to others, that was not going to work for many users, since most people would not have home-brew installed, so we needed to wrap it all up into the KStars App bundle to make it easier to use. So the drivers are built and bundled into the app now. They really can't be separated, since both KStars and the drivers depend on certain dynamic libraries that get bundled into the app and those libraries would not exist on your Mac outside of the app bundle unless you have home-brew, so they really do come together as one. A few years ago, we switched to craft to build everything because it is better suited for that purpose than home-brew, and it can certainly build the drivers now with no problem. The issue right now is that we are changing our craft recipes to update how it is done and get it working again with hopefully daily builds. But, we might have to update to QT6 as well. Home-brew is certainly also capable of building and installing all the library dependencies of the drivers, and then you could build the drivers. But I don't think I currently have a script set up to do that since craft has been working so much better for us overall.

Thank you for all the background info.
I tried once to build the 3rd party INDI driver myself but ran into a bunch of error messages. Then I realized that some of the LINUX distributions of KStars come with the drivers already precompiled and readily available.
Is the same possible for KStars on macOS? Of course it would make the package bigger because of all the extra libraries. It would certainly extend the usability of KStars on the Mac.

Well the KStars dmg that we are discussing does come with all the drivers already compiled and bundled into the app including the ones in the 3rd party repo that were working on MacOS at the time the dmg was built. Unless of course there was some kind of issue with the settings or the driver build option for that particular driver for some reason was turned off when it was built, or of course if there was a problem with building it at the time.

In terms of the Avalon driver, I do not know much about it or why it may or may not have been included in the last dmg. When I built it, I just used my script from before and if that driver was turned off in the settings then it would not have been included. You can always check the list of which ones are on or off at a particular time in the cmakelist and thus those should build in a dmg built that day, but of course that list can change over time for various reasons.

github.com/indilib/indi-3rdparty/blob/master/CMakeLists.txt

When binary factory was running we could have just recommended you just check a different daily build if a driver is missing or if an issue was fixed, but KDE changed that system and we will need to update our recipes accordingly.

Thank you for the detailed explanation and answer! Very helpful!!!

I checked the CMakeList and indeed, the AvalonUD is enabled/active.
option(WITH_AVALONUD "Install AvalonUD Drivers" On)

In EKOS, it keeps showing as an external source/driver, which is a bit confusing for me. See screenshot below.

So, I will rerun the tests soon and see if the problem with the calls to the mount from KStars are related to a different issue.

if it shows up like that, that means that for some reason that particular driver did not get built when I built the DMG for some reason. I do not know why it did not get built that day for certain. It may have been that someone was working on it, or maybe there was an issue on my computer with that one when the dmg was being built. At any rate, I had cleared out that directory and tried to start fresh when I had found out about the changes to the recipes and upgrading QT6, so I can't actually look at the files anymore to verify why that driver may not have built.