What happened to qt4-mac's qmake utility (re High Sierra v. Lion)?

Ian Wadham iandw.au at gmail.com
Thu Nov 23 06:37:27 UTC 2017

> On 23 Nov 2017, at 4:38 pm, Nicolas Pavillon <pavillon.nicolas at gmail.com> wrote:
> I don’t think the change in prefix is platform dependent. This happened quite some time ago to allow co-installation of both qt5 and qt4-mac (see https://trac.macports.org/changeset/140960). As far as ports are concerned, their compilation should have been fixed also quite some time ago.
> If you need to find specific qt4 components in your own codes, I imagine that setting QTDIR should be enough (just a wild guess), which
> is now set to ${prefix}/libexec/qt4.

Thanks, Nicolas, I might try that. Nice to see you are still around... :-)
Cheers, Ian W.

>> On Nov23, 2017, at 12:36, Ian Wadham <iandw.au at gmail.com> 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?
>> All the best, Ian W.

More information about the macports-users mailing list