So maybe we should just forget the cmake version - I am having trouble with it, too. I am going to try to re-emerge - If that doesn't work for me then I will have to revert my script anyway.
Well it is rather important, because we need a route to get a version of kstars that we can to edit, build, and test code in QT Creator. I have been doing that all along on my old laptop, but I need it to work on my new one. That route might use your script to get it all set up, or maybe we just want a series of steps. I had some issues with using on my new laptop the series of steps I had used to get it up and running on my old laptop, and I am having trouble with the version built using your script. It is very close to working and we do need to get it working somehow.
The version we have build using emerge is fully functional. But we need another build that we can edit in Qt Creator. Otherwise we can't really do any more OS X specific development. It is kind of vital.
Oh the emerge one works just fine, I did that earlier today with no problem! But we need one we can edit as well. It may be that we can load the emerge one into QT Creator and edit it somehow. But it is confusing.
Well yes, we were using the brew qt5 version for that. On my new MacBook Pro, I tried my series of steps for it. I wanted to try to make these use my installed qt instead of the brew qt5 by exporting the environment variable, but it refused and installed the brew qt5 anyway.
After all of that, I tried the cmake and it failed. I don't remember what it was now that failed, but it did. So then I asked Jamie if he could add a function to his script that would allow us to use his script to get a version that could be edited in qt creator. That would be easier than doing all of this anyway, especially if it works with without the homebrew qt5. It almost works now.
One of the files in github.com/haraldF/homebrew-kf5 probably checks for Qt5 path, just need to find out which one and see what we can do to overwrite it.
The following is just an idea and you can shoot me down for being a stupid one...
Maybe we should separate the build script and have one for emerge and one for cmake , maybe?
We know the emerge one works, I know I used it earlier this afternoon and it works from start to finish without an error.