Opened 14 years ago
Closed 14 years ago
#25476 closed defect (fixed)
qt4-mac fails when 10.4 or 10.5 SDK not installed
Reported by: | michaelld (Michael Dickens) | Owned by: | michaelld (Michael Dickens) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.1 |
Keywords: | wrong SDK | Cc: | Themanwithoutaplan |
Port: | qt4-mac |
Description
Summarizing ticket #25433, comments 21-23:
The issue is that qt4-* uses the 10.4 SDK by default and needs to be told otherwise when compiling under 10.5 or 10.6; if we don't upgrade the SDK, some Qt features don't compile or work. So, we chose the "minimal" upgrade -- to 10.5 -- for 10.5 and 10.6 (leaving 10.4 alone). But, if you don't have the 10.5 SDK installed (as could be the case on 10.6) then this upgrade doesn't work -- and, so, using the 10.6 SDK would probably make sense in that case.
Change History (8)
comment:1 Changed 14 years ago by michaelld (Michael Dickens)
Owner: | changed from macports-tickets@… to michaelld@… |
---|---|
Status: | new → assigned |
comment:2 Changed 14 years ago by michaelld (Michael Dickens)
comment:3 Changed 14 years ago by Themanwithoutaplan
It's configuring okay at least. I'll you know later if it's built okay.
Apple is pushing ahead with 10.6 and I don't blame you for not necessarily running it yet.
Changed section:
+++192,0 platform darwin 10 { if {![variant_isset universal] || ![info exists universal_sysroot]} { configure.args-append -sdk /Developer/SDKs/MacOSX10.6.sdk/ } }
comment:4 Changed 14 years ago by jmroot (Joshua Root)
Does it accept something like "-sdk /"? There's really no reason to use an SDK when targeting the platform you're building on.
comment:5 Changed 14 years ago by michaelld (Michael Dickens)
There should be no reason to have to specify a particular SDK except maybe when doing universal. Some people have reported that if the -sdk isn't set and the 10.4 SDK isn't installed then qt4 "loses it" and doesn't compile. It's easy enough to just set the SDK for the version of Darwin, which is what I'm putting together tonight. I'll also try "-sdk /" and see if it works.
comment:6 Changed 14 years ago by Themanwithoutaplan
Couldn't check for the flag while it was building. But just letting you know that it built okay.
comment:7 Changed 14 years ago by michaelld (Michael Dickens)
Glad to know it compiled OK; I'll make that change to the next checkin, possibly later today (July 1) but more likely tomorrow. Thanks for reporting back.
comment:8 Changed 14 years ago by michaelld (Michael Dickens)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Hopefully fixed in r69365. I'm going to close this ticket since I think your change is all that was needed.
Forgot to mention: If you want to try moving to the 10.6 SDK, edit the qt4-mac Portfile and change the string "MacOSX10.5.sdk" to "MacOSX10.6.sdk" and see if that works (just "sudo port install qt4-mac" since 'port' will do the cleaning for you because the Portfile was changed). I'd be curios to know if it works, as I'm not yet running 10.6 and so I can't fully test the changes I thinking of for this ticket.