[MacPorts] #27558: qt4-mac @4.7.1 adding 'framework' variants
MacPorts
noreply at macports.org
Mon Jan 17 11:02:02 PST 2011
#27558: qt4-mac @4.7.1 adding 'framework' variants
------------------------------------+---------------------------------------
Reporter: youngtaek.oh@… | Owner: michaelld@…
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.2
Keywords: | Port: qt4-mac
------------------------------------+---------------------------------------
Comment(by michaelld@…):
Replying to [comment:19 vitto.giova@…]:
> Mac OS X is DESIGNED to have frameworks instead of libraries so it makes
no sense to me that by default qt is built as library.
Actually, Qt 4.7.1 if configured without arguments will default to a
framework install on OSX/Darwin. On all other OSs it will default to non-
framework.
> I strongly suggest to have qt built as framework as default, with the
silly option to build with no_framework; if other packages break because
of qt built as framework, is other packager mantainers' problem.
I'd rather just have one or the other -- it makes error checking /
debugging easier (e.g., where the QtCore_Debug library is located; or, if
someone has an issue to do "otool -L ....QtCore..." & know where that
library is located). Most ports use PKGCONFIG or CMAKE (or QMAKE) for
building, and each of these "knows" how to find Qt headers and link to Qt
libraries. To the best of my knowledge, only a few ports care whether or
not Qt is installed as a framework or not, and we've patched those in the
past successfully.
As I've said, when 4.7.2 comes out I'll make the decision -- for various
reasons I'm strongly leaning towards going to "just framework".
--
Ticket URL: <https://trac.macports.org/ticket/27558#comment:21>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list