[MacPorts] #33030: qt4-mac-devel (4.8.0 final) fails to build (on Lion) - missing QtWebKit_debug
MacPorts
noreply at macports.org
Tue May 1 17:37:29 PDT 2012
#33030: qt4-mac-devel (4.8.0 final) fails to build (on Lion) - missing
QtWebKit_debug
--------------------------------------+-------------------------------------
Reporter: dev@… | Owner: michaelld@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.0.3
Keywords: qt4 lion | Port: qt4-mac-devel
--------------------------------------+-------------------------------------
Comment(by michaelld@…):
So, I've now fixed my internal qt4-mac to only use the build mkspecs,
which is good. I've fixed qt4-mac to install as library, framework,
library+universal, framework+universal, debug+library, debug+framework,
and debug+universal+framework. But this issue is still valid with
debug+universal+library. Well, it's actually still present in
debug+universal+framework too, but because of the way frameworks are
linked it's not an issue (frameworks in Qt do not link as debug, just
release; one uses a DYLD environment shell variable to access the debug
library). I can fix this issue either by changing how one links into
QtWebKit, or how the QtWebKit library / framework is created. I'm going
to try the latter tomorrow and see how far I get; if all else fails, then
I'll revert to the former since it should be pretty straight forward (just
a hack to a mkspec file). I'm surprised that Qt 4.8.1 builds correctly on
OSX when using default configure values, given this issue. This is the
last issue that I'm going to address before pushing the updates, btw.
Quite a journey getting to this point!
--
Ticket URL: <https://trac.macports.org/ticket/33030#comment:11>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list