[MacPorts] #49303: qt4-mac: Update to 4.8.7_2 Breaks CMake
MacPorts
noreply at macports.org
Fri Dec 11 03:07:28 PST 2015
#49303: qt4-mac: Update to 4.8.7_2 Breaks CMake
-------------------------------+-------------------------
Reporter: digitalriptide@… | Owner: michaelld@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.3.4
Resolution: | Keywords:
Port: qt4-mac |
-------------------------------+-------------------------
Comment (by rjvbertin@…):
Replying to [comment:19 mojca@…]:
> (Or use René's ideas of packaging Qt.)
Much as I appreciate the thought, if you refer to my way installing Qt
that doesn't actually provide a solution. qmake still gets installed in
${prefix}/libexec/qt${version}/bin, because Qt itself doesn't really give
you any other choice.
Actually, there *is* one aspect of my Qt ports that would indeed help
here: both support the `port select` mechanism to select a default
version. I think it was Michael even who suggested I add that feature, way
back; I'm not sure why he didn't implement it himself.
> technical reason why FindQt4.cmake would not be able to find Qt.
Of course, you can patch `FindQt4.cmake`. I can give you 2 more or less
technical reasons why this is less trivial than it sounds:
- The file is installed by `port:cmake`; to patch it with complete
observation of all principles would mean letting `port:cmake` depend on
`port:qt4-mac` (at the least it'd have to include the Qt4 PortGroup in
order to know where qmake v4 is to be found when installed). This will
probably lead to issues building the cmake GUI against Qt5.
- Many ports provide their own FindQt4.cmake ; `port:kdelibs4` installs
one for all KDE4 ports. You'd have to patch all of them or at least remove
the port-specific ones.
--
Ticket URL: <https://trac.macports.org/ticket/49303#comment:20>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list