I have also found an alternative way, and it also works quite nicely

step 1:
step 2:
step 3:
brew install it...
the conflict there is because of my manual install in the previous post to that, not really a problem as such.


step 4:
enjoy....

and yet another even better alternative, based on the previous one...

in the following folder: /usr/local/Homebrew/Library/Taps/haraldf/homebrew-kf5
run the following sed commands:
sed -i '.bak' 's/*args/"-DCMAKE_PREFIX_PATH=\/usr\/local\/Cellar\/qt5\/5.7.0", *args/g' *.rb
sed -i '/depends_on "qt5"/,/^/d' *.rb

and then you can brew install what you need...

So unless my above steps are totally wrong, we are now able to save HOURS!!!!! by not having to wait for a custom compile Qt5 installation tada....
Jamie's script, the cmake option will only take a few minutes now.

I don't like the word "manual"

way-back-when - before we started using emerge - the qt install was with the dbus installed. I still have all of the kf5 installed on the machine I used yesterday. This is what the related steps looked like back then:

PSA: Note to anyone jumping in and thinking that running this stuff will fix something - this is a look back in time
The reason we moved to the emerge method was that it was faster. But when we are doing this over and over - is it really? Is the emerge what lets us create a dmg, or can we do this with just the brew stuff? I don't know enough about building software on mac, let alone QT. The brew one has the deploy tool: /usr/local//Cellar/qt5/5.7.0/bin/macdeployqt.

Once that first brew install qt5 --with-dbus is done it doesn't need to be done again.

I have a bunch of errands to do today so probably won't be able to do much at all

Jamie, have a read through my last comments, I do believe I've cracked the KF5 issue we had as in waiting hours... for Qt5 to compile.

Due to the time it took, we moved to emerge only as installing the Qt5 dmg file is way quicker to compile it.
But now, I've found a super quick way. So, if someone wants emerge or cmake, the options are there.

OK, so this can be automated - you can do the same with the DBUS on the plotting, right? Can you try runningand see what that does? it won't work when you try to mount it - but if it looks like it is trying then we might be back to a single workflow

Yeah, commends crossed in the ether. it sounds promising - does kstars use dbus? it sure shows up in a lot of files. Maybe without it something gets degraded

I do not have:


let me install all the KF5 stuff, and run the build script with the cmake option first. hold on.

If we end up going this route we can always fork that kf5 repo and make the changes there

Sound good to me, ok off to install this KF5 now, found any issue I need to resolve first).

just hit a road block which I need to overcome.

Maybe make sure that you don't have any kf5 stuff already installed?