One really good item to note. Because we have now been deploying everything in the app, the final build should be self-sufficient. So I tried copying the app to my applications directory and deleting everything in indiroot. It still worked! Which means if we royally mess up either the cmake version or the emerge version, as long as you have a copy of the app on your computer somewhere from a successful build, you can still use kstars!
I had to change one line of his code though, because my QT5 somehow installed to that other directory. I used the default as well, so I don't know why ours are different. Perhaps he used a different installer than I did.
sed -i '.bak' 's/*args/"-DCMAKE_PREFIX_PATH=\/Users\/rlancaste\/Qt\/5.7\/clang_64\/", *args/g' *.rb
For the script, would it work for us to use ~ for this instead of the path above?
Yes, I saw this exact problem. I just now had to install kf5-kauth and kf5-knotifications because brew didn't try to install them when it called for it as dependency like it did the others. So we should make a note of any others and maybe do those first to get this whole thing automated.
Now I am on to the cmake build of kstars. so far so good!!! It was so fast compared to when we had to use brew qt5. Nice work Stephane!! Now lets hope it works!
If you are at the cmake of kstars then I think it's in the bag. As long as you've got all the KF5 stuff installed...
I've spent the entire day trying to crack this mystery of Qt5 compile stuff, it was by accident that I had an Eureka moment.... I saw an error on my screen and followed the path..., realised you could brew --interactive etc.... the rest is history as they say.