On Feb 16, 2012, at 22:38, Eric Cronin wrote: > On Feb 16, 2012, at 2:10 PM, Jeremy Huddleston wrote: > >> As many of you may have noticed, XCode 4.3 was released today. The >> installation of XCode 4.3 is a bit different than previous releases and will >> require some updates to the macports installation wiki. >> >> 1) For starters, XCode 4.3 is self contained in an app bundle. You no >> longer need to go through an installer. Just grab it from the App Store. >> >> 2) After it finishes downloading, make sure you open XCode.app before >> "jumping in" ... this will allow you to agree to the Terms Of Service to >> avoid errors if you try building a port that uses xcodebuild. >> >> 3) Since XCode is now an app, you no longer have the "UNIX Development" (or >> similar, I can never remember the exact naming) installed to / by the >> installer. If you goto XCode's preferences, you will see a "Downloads" tab. >> You should see it now listed in there as an optional download. Also, I >> think XCode will notify you on launch if it sees an older toolchain >> installed to /, so you were probably be told about this when you did step 2 >> anyways. >> >> 4) Go about using MacPorts as normal ... >> >> 5) Report any bugs (including corrections to these instructions) that you >> find … > > The main problem I ran in to is that a number of our ports cache the compiler > they were built with internally (libtool, python, apr), and then a number of > other ports interrogate those first set of ports to get the paths of tools to > use, resulting in attempts to compile using /Developer/.../llvm-g*-4.2, which > no longer exists. This is probably a bug with the dependent ports from a > MacPorts angle, since we want the compiler the Portfile/base specifies used, > not what 'apr-1-config --cc' returns. Force reinstalling the ports caching > paths to the toolchain allowed the remaining ports to be built. Some variant > of the migration upgrade steps is probably required to make sure nothing has > /Developer paths stored away…
And now we really really need binary packages to include what version of Xcode they were built on, not just what version of OS X they were built on. :( And we should be keeping that information in the registry as well. _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
