> On 23 Nov 2017, at 4:38 pm, Ryan Schmidt <ryandes...@macports.org> wrote: > > > On Nov 22, 2017, at 21:36, Ian Wadham wrote: > >> I have been setting up a new MacBook Pro 13-inch with High Sierra. >> Macports is building and running fine with qt4-mac, kdegames4 and kmymoney4 >> requested and a long list of dependencies installed. >> >> Now I am trying to resurrect some of the KDE 4 source-code and applications >> I used to work on when I was a KDE developer. I brought across a bunch of >> source >> from my old MacBook Pro (2011 vintage and using Lion). But when I went to >> build >> it CMake failed during its checks of the software and hardware environment, >> which >> it does before starting to generate a makefile and build. >> >> Specifically, CMake could not find qmake, Qt’s utility for generating >> builds. Using >> “port contents” I found that qt4-mac @4.8.7_5 has qmake installed at >> /opt/local/bin >> on Lion, but on High Sierra it is at /opt/local/libexec/qt4/bin, which is >> not in my $PATH. >> >> So why has qmake moved? >> >> And what should I add to my $PATH, /opt/local/libexec/qt4/bin? Or would >> /opt/local/libexec >> be enough (and more general)? Or perhaps CMake needs some option? > > qmake and other qt programs and files moved so that the qt4-mac and qt5 ports > could be installed simultaneously. Ports using qt are meant to use the > various qt portgroups, which set variables that the port can use to access > the locations of those files. If you're trying to build your own software > outside of MacPorts but using MacPorts qt, I guess you'll have to put the > right path into your $PATH. The right path is the one that contains the > binary you want to use. I don't know if modifying the $PATH is enough for > cmake to be able to find things.
Good answer. Thanks, Ryan. Putting Qt’s libexec on the $PATH does placate CMake and the build then proceeds normally. Cheers, Ian W.
