Hi Rob,
Thank you for all this information, this help me a lot.
It take up to this week until I find some free time to continue to work on this. But now this is almost complete and I have some binaries build with Craft that can be tested.
The scripts build and install INDI in any .app, independently of the application itself.
I put the build scripts in a github repo to make this more easy to share and correct any error.
github.com/pchev/indi-mac
For testing I update my IndiStarter application that can now use the embedded INDI server.
The point 1. in your last message was very useful, I find the environment variable to set in Kstars source. After I do that in my application there is no more problem with the skeleton files.
I can do only very limited test with the simulators because my only "Mac" is a virtual machine running on Linux KVM.
So I am very interested by any real test that can be done by installing the application from:
sourceforge.net/projects/indistarter/files/testing/
The application documentation is here:
github.com/pchev/indistarter/wiki
Be sure to set a log file in the Setup options to get any error from the INDI server or driver.
This IndiStarter application can be a temporary solution for the point 2. , provide a GUI to start INDI on Mac. This give some time to discuss what solution we prefer on the long term. As I already say I not see IndiStarter as a permanent solution because I write it using FreePascal and this is not a language know by other INDI developers.
Tell me if you change the script for the repo split or inclusion in standard KDE craft so I can update my script.
Patrick