Re: Xcode 4.3 and command line tools version mismatches

On Mar 23, 2012, at 7:23 AM, Daniel Ericsson wrote: > On 22 mar 2012, at 12:04, Ryan Schmidt wrote: > >> But this fails if the user has installed Xcode 4.3 but not Xcode 4.3's >> command line tools. >> >> Is there a way we can discover the version of Xcode

Re: Xcode 4.3 and command line tools version mismatches

On 22 mar 2012, at 12:04, Ryan Schmidt wrote: > But this fails if the user has installed Xcode 4.3 but not Xcode 4.3's > command line tools. > > Is there a way we can discover the version of Xcode that the installed > command line tools belong to? If so, we should modify ba

Xcode 4.3 and command line tools version mismatches

Now that with Xcode 4.3 the command line tools are a separate installation, it's becoming common for users to have a different version of Xcode than of the command line tools. For example: https://trac.macports.org/ticket/30598#comment:17 And: http://lists.macosforge.org/pipermail/mac

Re: Please test branches/release_2_0 with Xcode 4.3

On Feb 27, 2012, at 07:09, Andrea D'Amore wrote: > On Mon, Feb 27, 2012 at 14:06, Rainer Müller wrote: >> On 02/27/2012 10:01 AM, Andrea D'Amore wrote: >>> How do you guys handle using different mp versions? > >> I have /opt/local running trunk and a separate /opt/release_2_0 running >> the releas

Re: Please test branches/release_2_0 with Xcode 4.3

On 2012-02-26 16:26 , Clemens Lang wrote: > It's not a large blocker IMHO though, because > grep -R -E -i --exclude-dir=.svn "build.type[ \t]*bsd" . > shows 9 ports using bsdmake. Those are: > ppmd > scud > bsdiff > libcipher > fortune > dsocks > boxb

Re: /Developer symlink with xcode 4.3

Hello Dan, Le 29 févr. 2012 à 00:10, Dan Ports a écrit : > The problem here is that the python27 port records the path to the > compiler that was used to build it, and uses that compiler to build > modules like py27-tkinter. In your case, that's the compiler in > /Developer. Thanks, your diagnost

Re: /Developer symlink with xcode 4.3

On Tue, Feb 28, 2012 at 11:26:48PM +0100, Benoit T wrote: > Why again is it that one may have to symlink > /Applications/Xcode.app/Contents/Developer to /Developer ? You shouldn't ever have to do this. > I had to do that in order to build py27-tkinter, a trivial package that > does not have the s

/Developer symlink with xcode 4.3

kages that came out during the last few days when i ran svn HEAD while waiting for 2.0.4. I don't know enough about the operation of macports to know where the incorrect path to llvm-gcc-4.2 comes from and to sort that out from the recent chatter about moving to Xcode 4.3. Is that just a bug wi

Re: Please test branches/release_2_0 with Xcode 4.3

On Mon, Feb 27, 2012 at 14:06, Rainer Müller wrote: > On 02/27/2012 10:01 AM, Andrea D'Amore wrote: >> How do you guys handle using different mp versions? > I have /opt/local running trunk and a separate /opt/release_2_0 running > the release_2_0 branch. The important step is that you need to set

Re: Please test branches/release_2_0 with Xcode 4.3

On 02/27/2012 10:01 AM, Andrea D'Amore wrote: > How do you guys handle using different mp versions? I have /opt/local running trunk and a separate /opt/release_2_0 running the release_2_0 branch. The important step is that you need to set applications_dir and frameworks_dir to a separate location

Re: Documentation for Xcode 4.3

On Tue, Feb 21, 2012 at 15:52, Jeremy Lavergne wrote: >  1 > http://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/wa/getSoftware?bundleID=21048 >  2 > http://connect.apple.com/cgi-bin/WebObjects/MemberSite.woa/wa/getSoftware?bundleID=21047 >  3 > http://connect.apple.com/cgi-bin/WebObject

Re: Please test branches/release_2_0 with Xcode 4.3

On Tue, Feb 21, 2012 at 08:04, Dan Ports wrote: > I have been testing this and think we're close to ready for release. > I haven't had any problems with it once correctly set up. IIRC this has been discussed but I cannot find the mail in archive: I usually have 2.0.99 installed but lately I wante

Re: Please test branches/release_2_0 with Xcode 4.3

far as I understand the current state, the admin user is _forced_ > to run Xcode 4.3 at least once to let create it a > com.apple.dt.Xcode.plist file in the admin's preferences directory. > BUT: what if the user intentionally doesn't want to do that, wants to > avoid that (fo

Re: Please test branches/release_2_0 with Xcode 4.3

Hi, On Tue, Feb 21, 2012 at 05:14:36PM +1100, Joshua Root wrote: > Seems to work OK in my basic testing. The sooner we catch any problems > and get a release out, the better. Xcode 4.3 seems to no longer ship bsdmake, which breaks all ports with build.type set to bsd. It's not a la

Re: Please test branches/release_2_0 with Xcode 4.3

Hi! Concerning: http://lists.macosforge.org/pipermail/macports-dev/2012-February/017914.html Problem: In Changeset 89994 on https://trac.macports.org/changeset/89994, trunk/base/src/macports1.0/macports.tcl I see, that user's xcode 4.3 plist file ${user_home}/Library/Prefer

Re: Please test branches/release_2_0 with Xcode 4.3

On Mon, Feb 20, 2012 at 11:04:19PM -0800, Dan Ports wrote: > Right now, what I'm worried about are the kind of errors we'll get if > Xcode is not properly installed/configured. There are a couple > non-obvious steps you have to take and the results can be surprising: I added some additional warnin

Re: Running xcodebuild as macports user (Was Re: XCode 4.3)

dleston wrote: > >> Please try running 'sudo xcodebuild' and accepting the license as root. >> That should allow all users on the system to use XCode (including the >> macports user). >> >> --Jeremy >> >> On Feb 18, 2012, at 02:11, Joshua Ro

Documentation for Xcode 4.3

When we update the documentation for the next release, be sure to include all the disk images that might be needed (or download options from within xcode): Xcode [1] for the majority of the build chain, Command Line Tools [2] for xcodebuild and Auxiliary Tools for Xcode [3] for PackageMaker. 1

Re: another Xcode 4.3 note: autotools missing

On Feb 19, 2012, at 9:57 PM, Dan Ports wrote: > I haven't found anything that depends on autoconf being in /usr/bin, > but I did see a couple ports (metakit and pfe) that try to copy > /usr/bin/glibtool into their build directory. Somewhere out there, I hear the sound of MacPorts' decision to i

Re: Please test branches/release_2_0 with Xcode 4.3

On Tue, Feb 21, 2012 at 05:14:36PM +1100, Joshua Root wrote: > Seems to work OK in my basic testing. The sooner we catch any problems > and get a release out, the better. I have been testing this and think we're close to ready for release. I haven't had any problems with it once correctly set up.

Running xcodebuild as macports user (Was Re: XCode 4.3)

Please try running 'sudo xcodebuild' and accepting the license as root. That should allow all users on the system to use XCode (including the macports user). --Jeremy On Feb 18, 2012, at 02:11, Joshua Root wrote: > So it looks like we can't support Xcode 4.3 unti

Please test branches/release_2_0 with Xcode 4.3

Seems to work OK in my basic testing. The sooner we catch any problems and get a release out, the better. - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: Xcode 4.3 issues, potential solutions

On Feb 20, 2012, at 5:40 PM, Dan Ports wrote: > On Mon, Feb 20, 2012 at 07:41:00AM -0800, James Berry wrote: >> Any more information you can give about the failure mode would be >> appreciated. According to my testing, xcode-select -print-path can be safely >> run even if you've never agreed to

Re: Xcode 4.3 issues, potential solutions

On Mon, Feb 20, 2012 at 07:41:00AM -0800, James Berry wrote: > Any more information you can give about the failure mode would be > appreciated. According to my testing, xcode-select -print-path can be safely > run even if you've never agreed to the Xcode agreement, so I don't think > that's what

Re: perl and configure.compiler (was Re: XCode 4.3)

On Feb 19, 2012, at 9:40 PM, Dan Ports wrote: > On Sun, Feb 19, 2012 at 04:45:44PM -0500, Daniel J. Luke wrote: >> It's somewhat debatable that 'fixing' this by having the modules build with >> configure.compiler is really the right thing here (there is a reason why >> upstream tries to make both

Re: XCode 4.3

On Feb 19, 2012, at 8:06 PM, Ryan Schmidt wrote: > On Feb 19, 2012, at 16:11, Art McGee wrote: I've got MacPorts, Fink, and Pkgsrc co-existing on my machine, and they're working OK so far. >>> >>> I hope that means that you have both MacPorts and Fink configured for >>> nonstandard pref

Re: Xcode 4.3 issues, potential solutions

On Feb 20, 2012, at 3:15 AM, Dan Ports wrote: > On Fri, Feb 17, 2012 at 10:32:48AM -0800, James Berry wrote: >>> (2) If developer_dir is not set, or is not correct, do the following, >>> in order >>> >>> (a) Use any valid value from: xcode-select -print-path (the >>> user has c

Re: Xcode 4.3 issues, potential solutions

On Fri, Feb 17, 2012 at 10:32:48AM -0800, James Berry wrote: > > (2) If developer_dir is not set, or is not correct, do the following, > > in order > > > > (a) Use any valid value from: xcode-select -print-path (the > > user has chosen an Xcode, or Xcode's default is correct) [.

Re: Xcode 4.3 Command Line Tools installer glitch

On 02/17/2012 05:03 AM, Jack Howarth wrote: I've confirmed that for both the clean install of Xcode 4.3/Command Line Tools as well as the upgrade install of Xcode 4.3/Command Line Tools over Xcode 4.2.1 that the developer directory path isn't being set. This results in 'xcode

Re: another Xcode 4.3 note: autotools missing

On Feb 19, 2012, at 23:57, Dan Ports wrote: > but I did see a couple ports (metakit and pfe) that try to copy > /usr/bin/glibtool into their build directory. They should use MacPorts glibtool instead. ___ macports-dev mailing list macports-dev@lists.m

another Xcode 4.3 note: autotools missing

Another difference in Xcode 4.3 that I haven't seen mentioned yet: it doesn't install autoconf, automake, (g)libtool, and friends. I'm assuming that this mostly isn't going to be a problem, since use_autoconf will pull in the right dependencies, but I thought I'd mentio

Re: XCode 4.3

On Sun, Feb 19, 2012 at 04:45:44PM -0500, Daniel J. Luke wrote: > It's somewhat debatable that 'fixing' this by having the modules build with > configure.compiler is really the right thing here (there is a reason why > upstream tries to make both perl and its modules build with the same > compil

Re: XCode 4.3

On Feb 19, 2012, at 16:11, Art McGee wrote: >>> I've got MacPorts, Fink, and Pkgsrc co-existing on my machine, and >>> they're working OK so far. >> >> I hope that means that you have both MacPorts and Fink configured for >> nonstandard prefixes, meaning your MacPorts is somewhere other than >>

Re: XCode 4.3

On Fri, Feb 17, 2012 at 08:15:43AM -0500, Eric Cronin wrote: > audiofile would not update correctly until I rebuilt libtool, at which point > it did. I don't know if audiofile or libtool is to blame there, but libtool > was where it was learning /Developer from? Well, in the case of audiofile,

Re: XCode 4.3

On Sun, Feb 19, 2012 at 02:11:41PM -0800, Art McGee wrote: > >> I've got MacPorts, Fink, and Pkgsrc co-existing on my machine, and > >> they're working OK so far. > > > > I hope that means that you have both MacPorts and Fink configured for > > nonstandard prefixes, meaning your MacPorts is somewh

Re: XCode 4.3

>> I've got MacPorts, Fink, and Pkgsrc co-existing on my machine, and >> they're working OK so far. > > I hope that means that you have both MacPorts and Fink configured for > nonstandard prefixes, meaning your MacPorts is somewhere other than > /opt/local and your Fink is somewhere other than /sw

Re: XCode 4.3

On Feb 19, 2012, at 2:29 AM, Ryan Schmidt wrote: > On Feb 19, 2012, at 00:35, Dan Ports wrote: >> (One could argue that it's a bug that, e.g. perl modules build using >> the compiler that built perl rather than configure.compiler, but I'm >> not sure that's something we either want to or can easily

Re: XCode 4.3

> What's your system version? Perhaps the version of xcode-select you have is > less capable? > > % xcode-select -version > xcode-select version 2307. Aha, that explains it: $ which xcode-select /usr/bin/xcode-select $ xcode-select -version xcode-select version 2003. I'm on 10.7.3 (11D50) and

Re: XCode 4.3

On Feb 19, 2012, at 07:11, Art McGee wrote: > I've got MacPorts, Fink, and Pkgsrc co-existing on my machine, and > they're working OK so far. I hope that means that you have both MacPorts and Fink configured for nonstandard prefixes, meaning your MacPorts is somewhere other than /opt/local and

Re: XCode 4.3

using either /Applications/Xcode.app or the longer version seem to > accomplish the same thing. My xcode-select doesn't have any trouble with the > shorter version. > > % sudo xcode-select -switch /Applications/Xcode.app && xcode-select > -print-path && xc

Re: XCode 4.3

ave any trouble with the shorter version. % sudo xcode-select -switch /Applications/Xcode.app && xcode-select -print-path && xcodebuild -version /Applications/Xcode.app/Contents/Developer Xcode 4.3 Build version 4E109 What's your system version? Perhaps the version of xcode

Re: XCode 4.3

usr/bin/xcodebuild' (No such file or directory) I also tried an experiment, to see if Xcode.app can only reside in /Applications, and it doesn't seem like it has to. I've chosen to place Xcode 4.3 and all the other downloadable utilities in their own directory, leaving 4.2.1 in

Re: XCode 4.3

Aljaž Srebrnič wrote: > Unfortunately, the user "macports" has its home directory in /var/empty, so > even if I set a home via -H, it will have no effect (/var/empty is read only > AFAIK) > > Aljaž Srebrnič hmmm ... how about : # prefix with 'sudo' -or- 'ssh root@localhost' mkdir -p /opt/local

Re: XCode 4.3

On Feb 19, 2012, at 00:35, Dan Ports wrote: > (One could argue that it's a bug that, e.g. perl modules build using > the compiler that built perl rather than configure.compiler, but I'm > not sure that's something we either want to or can easily change.) Well as you know it was a bug that perl m

Re: XCode 4.3

On Sun, Feb 19, 2012 at 02:42:38PM +1100, Joshua Root wrote: > Remember the location of the invoking user's home dir by saving $HOME > when we start up. Set HOME at the macports level to > ${prefix}/var/macports/home. Copy or link the Xcode plist from the > user's home into ${prefix}/var/macports/h

Re: XCode 4.3

On Fri, Feb 17, 2012 at 05:51:30PM +1100, Joshua Root wrote: > No. This is exactly as big a change as Xcode 4.1 -> 4.2, which also > changed the default compiler path. Well, it's a bit different in that the previous compiler path is no longer even valid. That didn't happen with the 4.2 upgrade. I

Re: XCode 4.3

On 2012-2-19 05:09 , Dan Ports wrote: > On Sat, Feb 18, 2012 at 08:32:40AM -0800, James Berry wrote: >> - The record of whether you've agree to the license is stored per-user >> in ~/Library/Preferences/com.apple.dt.Xcode.plist: > [...] >> Maybe we need to create a macports user home at some

Re: XCode 4.3

On 2012-2-19 03:32 , James Berry wrote: > Just a bit of information: > > - The record of whether you've agree to the license is stored per-user > in ~/Library/Preferences/com.apple.dt.Xcode.plist: > > > "http://www.apple.com/DTDs/PropertyList-1.0.dtd";> > > > IDELastGMLicenseAgre

Re: XCode 4.3

On Feb 18, 2012, at 10:09 AM, Dan Ports wrote: > On Sat, Feb 18, 2012 at 08:32:40AM -0800, James Berry wrote: >> - The record of whether you've agree to the license is stored per-user >> in ~/Library/Preferences/com.apple.dt.Xcode.plist: > [...] >> Maybe we need to create a macports user h

Re: XCode 4.3

On Sat, Feb 18, 2012 at 08:32:40AM -0800, James Berry wrote: > - The record of whether you've agree to the license is stored per-user > in ~/Library/Preferences/com.apple.dt.Xcode.plist: [...] > Maybe we need to create a macports user home at something like > /opt/local/users/macports, wit

Re: XCode 4.3

On Sat, Feb 18, 2012 at 09:11:03PM +1100, Joshua Root wrote: > So it looks like we can't support Xcode 4.3 until there's a fix or > workaround for this problem. I've added some notices to the web site. I don't recall if the installation of Xcode via the App Store aut

Re: XCode 4.3

acports, with no access except to /opt/local/users/macportsLibrary/Preferences… ? James On Feb 18, 2012, at 2:11 AM, Joshua Root wrote: > So it looks like we can't support Xcode 4.3 until there's a fix or > workaround for this problem. I've added some notices to the web site

Re: XCode 4.3

> Because locate never has to update its db? Because it updates much, much faster after a large install. smime.p7s Description: S/MIME cryptographic signature ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/

Re: XCode 4.3

So it looks like we can't support Xcode 4.3 until there's a fix or workaround for this problem. I've added some notices to the web site. On 2012-2-18 06:06 , Jeremy Huddleston wrote: > I'm sorry I don't have a good solution for you, so I filed a radar. > &g

Re: clang moved in Xcode 4.3

On 2012-2-18 13:17 , Jack Howarth wrote: >It appears that the following change will be required for Xcode 4.3 in > port's > /opt/local/share/macports/Tcl/port1.0/portconfigure.tcl due to the fact that > clang/clang++ > only resides in /usr/bin now It doesn't onl

Re: XCode 4.3

On 2012-2-18 11:19 , Jeremy Lavergne wrote: >> It does have the correct kMDItemCFBundleIdentifier, and the mdfind >> command does work now, although it didn't before... weird. > > Probably wasn't done indexing for whatever reason--long live locate. hehe Because locate never has to update its db?

Re: Xcode 4.3 missing X1SDK?

On Feb 17, 2012, at 11:01 PM, Ryan Schmidt wrote: >> >> "Yep, Apple has depreciated it. They give you a link to download quartz >> when you launch X11.app in /Applications/Utilities" >> >> () > > *X*Quartz, please. Quartz is a graphics techno

clang moved in Xcode 4.3

It appears that the following change will be required for Xcode 4.3 in port's /opt/local/share/macports/Tcl/port1.0/portconfigure.tcl due to the fact that clang/clang++ only resides in /usr/bin now --- portconfigure.tcl.orig 2012-02-17 21:00:58.0 -0500 +++ portconfigur

Re: Xcode 4.3: where do xcode-select, xcodebuild, xcrun, etc, come from?

On Fri, Feb 17, 2012 at 02:45:23PM -0800, James Berry wrote: > (1) Do these tools exist on a machine if Xcode has never been > installed? (i.e., are they part of the core os?) Yes -- it looks like they are installed by the 10.7.3 update. Dan -- Dan R. K. Ports MIT CSAIL

Re: Xcode 4.3: where do xcode-select, xcodebuild, xcrun, etc, come from?

On Feb 17, 2012, at 2:45 PM, James Berry wrote: > The idea behind Xcode 4.3, as I understand it, is that it can be a > first-class App Store app: it doesn't need to install anything as root, or > outside of its sandbox: it uses external installers for this (witness the > C

Re: XCode 4.3

> It does have the correct kMDItemCFBundleIdentifier, and the mdfind > command does work now, although it didn't before... weird. Probably wasn't done indexing for whatever reason--long live locate. hehe smime.p7s Description: S/MIME cryptographic signature _

Re: XCode 4.3

On Fri, Feb 17, 2012 at 03:05:51PM -0800, James Berry wrote: > It would be interesting to know what xcode-select -print-path returns at this > point. Sure would. Unfortunately, I changed the path before I thought to try that. (Things do seem to be working now that I've done that, BTW.) > > Yes,

Re: XCode 4.3

On Feb 17, 2012, at 3:02 PM, Dan Ports wrote: > On Fri, Feb 17, 2012 at 02:53:13PM -0800, James Berry wrote: >> - Was Xcode 4.3 installed at that point? >> >> - Had Xcode been run after the install? (In other words, had you agreed to >> the license?) > &g

Re: XCode 4.3

On Fri, Feb 17, 2012 at 02:53:13PM -0800, James Berry wrote: > - Was Xcode 4.3 installed at that point? > > - Had Xcode been run after the install? (In other words, had you agreed to > the license?) Yes, I had installed Xcode 4.3, launched it, accepted its offer to re

Re: XCode 4.3

Hi Dan, On Feb 17, 2012, at 2:43 PM, Dan Ports wrote: > On Fri, Feb 17, 2012 at 12:58:56PM -0800, James Berry wrote: >> On Feb 17, 2012, at 12:41 PM, Daniel J. Luke wrote: >>> I had 4.2 installed, downloaded 4.3 from the app store, ran new Xcode >>> (4.3), told it t

Xcode 4.3: where do xcode-select, xcodebuild, xcrun, etc, come from?

The idea behind Xcode 4.3, as I understand it, is that it can be a first-class App Store app: it doesn't need to install anything as root, or outside of its sandbox: it uses external installers for this (witness the Command Line Tools installer, etc). So if that is indeed the case, I h

Re: XCode 4.3

On Fri, Feb 17, 2012 at 12:58:56PM -0800, James Berry wrote: > On Feb 17, 2012, at 12:41 PM, Daniel J. Luke wrote: > > I had 4.2 installed, downloaded 4.3 from the app store, ran new Xcode > > (4.3), told it to uninstall 4.2 (/Developer and the installer from > > /Applicat

Re: Xcode 4.3 missing X1SDK?

On Feb 17, 2012, at 00:26, Guido wrote: > Jack Howarth wrote: > >> I hope this isn't pointing to Apple deprecating >> X11 completely out of Mac OS X with Mountain Lion. Sigh. > > > "Yep, Apple has depreciated it. They give you a link to download quartz > when you launch X11.app in /Applicatio

Re: XCode 4.3

On Feb 17, 2012, at 3:58 PM, James Berry wrote: >> I had 4.2 installed, downloaded 4.3 from the app store, ran new Xcode (4.3), >> told it to uninstall 4.2 (/Developer and the installer from /Applications), >> had it install the command line tools, quit and xcode-select -prin

Re: XCode 4.3

e done for you when you launch Xcode.app for the first time. > > That did not happen for me. > >> If you have Xcode 4.2 installed, then download Xcode 4.3, and then just run >> Xcode.app, it should take care of the xcode-select of this for you. I'm >> curious why

Re: XCode 4.3

> If you have Xcode 4.2 installed, then download Xcode 4.3, and then just run > Xcode.app, it should take care of the xcode-select of this for you. I'm > curious why it didn't work in your case, but that magic isn't my specialty =/ > > FWIW, I have one Lion machin

Re: XCode 4.3

rted using compilers in /Developer/usr/bin is that >> llvm-gcc-4.2 wasn't installed in /usr/bin on Leopard. >> >> - Josh > > Josh, > While using /usr/bin makes sense, port would need to be modified to > sanity check that the developer directory path is set. Apple

Re: Xcode 4.3 issues, potential solutions

On Feb 17, 2012, at 8:05 AM, James Berry wrote: > Sounds like there are at least several issues that MacPorts is facing with > Xcode, not all of which are new: > > (1) Make sure the Xcode terms have been accepted > > (2) Find the proper Xcode is use. We can no longer assume /Develo

Xcode 4.3 issues, potential solutions

Sounds like there are at least several issues that MacPorts is facing with Xcode, not all of which are new: (1) Make sure the Xcode terms have been accepted (2) Find the proper Xcode is use. We can no longer assume /Developer (3) Ensure the command line tools have been i

Re: XCode 4.3

> As expected, a great number of ports don't actually need Xcode to build. Do > you think it'd be worthwhile indicating that people can get by with just the > command line tools until they see an xcodebuild error message? Specifically, this is the error a user who installed only the Command Line

Re: XCode 4.3

> 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.

Re: XCode 4.3

Leopard. > > - Josh Josh, While using /usr/bin makes sense, port would need to be modified to sanity check that the developer directory path is set. Apple neglected to have the post installation scripts in Xcode 4.3's Command Line Tool installer do that with... sudo xcode-select -sw

Re: Xcode 4.3 Command Line Tools installer glitch

>> sudo xcode-select -switch /Applications/Xcode.app > > > You should specify the new /Developer directory: > "sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer" does > work. Both forms work for me. ___ macports-dev mailing list ma

Re: XCode 4.3

On Feb 17, 2012, at 1:56 AM, Joshua Root wrote: > On 2012-2-17 15:38 , Eric Cronin wrote: >> 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

Re: XCode 4.3

On 2012-2-17 18:45 , Jeremy Huddleston wrote: > > Also, another thing to note is that the command line tools + SDK are > available as a separate download. If you don't need any parts of XCode > itself, you can probably get by with just installing these bits, but I > wouldn't recommend it for the

Re: XCode 4.3

On Feb 16, 2012, at 9:05 PM, Jeremy Lavergne wrote: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.  Do you know i

Re: XCode 4.3

On 2012-2-17 15:38 , Eric Cronin wrote: > 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

Re: XCode 4.3

On 2012-2-17 16:13 , Bjarne D Mathiesen wrote: > Ryan Schmidt wrote: >> >> On Feb 16, 2012, at 23:03, Jeremy Lavergne wrote: >> 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. :( An

Re: Xcode 4.3 missing X1SDK?

Jack Howarth wrote: > I hope this isn't pointing to Apple deprecating > X11 completely out of Mac OS X with Mountain Lion. Sigh. "Yep, Apple has depreciated it. They give you a link to download quartz when you launch X11.app in /Applications/Utilities" (

Re: XCode 4.3

Jeremy Lavergne wrote: >> How important is this release of XCode 4.3 if all you use XCode for is >> compiling macports stuff ??? > > Mac users race to grab updates as the method of realizing implications of > upgrades. RTFM only happens once things have gone wrong ;-) >

Re: Xcode 4.3 Command Line Tools installer glitch

On Feb 17, 2012, at 6:04 AM, Jack Howarth wrote: > until the user explicitly executes... > > sudo xcode-select -switch /Applications/Xcode.app You should specify the new /Developer directory: "sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer" does work. Guido -- https:/

Re: XCode 4.3

> 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.

Re: XCode 4.3

Ryan Schmidt wrote: > > On Feb 16, 2012, at 23:03, Jeremy Lavergne wrote: > >>> 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 regist

Re: XCode 4.3

> How important is this release of XCode 4.3 if all you use XCode for is > compiling macports stuff ??? Mac users race to grab updates as the method of realizing implications of upgrades. RTFM only happens once things have gone wrong ;-) ___ ma

Re: XCode 4.3

Eric Cronin wrote: > On Feb 16, 2012, at 2:10 PM, Jeremy Huddleston wrote: >> Hi, >> >> 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

Re: XCode 4.3

On Feb 16, 2012, at 23:03, Jeremy Lavergne wrote: >> 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. > > Never though

Re: XCode 4.3

> 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. Do you know if there's something we can run to test if the ToS has already been ac

Re: XCode 4.3

> 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. Never thought I'd say it: conveniently we don't have a Lion buildbot.

Re: XCode 4.3

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 >> req

Re: XCode 4.3

On Feb 16, 2012, at 2:10 PM, Jeremy Huddleston wrote: > Hi, > > 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. >

XCode 4.3

Hi, 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

Xcode 4.3 Command Line Tools installer glitch

I've confirmed that for both the clean install of Xcode 4.3/Command Line Tools as well as the upgrade install of Xcode 4.3/Command Line Tools over Xcode 4.2.1 that the developer directory path isn't being set. This results in 'xcodebuild -version' producing the error m

Re: Xcode 4.3 missing X1SDK?

On Feb 16, 2012, at 11:43 AM, Jack Howarth wrote: > Does anyone know what the situation is for Xcode 4.3 vs X11 SDK? > The Xcode 4.3 installation doesn't install the Command Line Tools by > default and installing Xcode 4.3 from the AppStore left the Downloads > preference p

Xcode 4.3 missing X1SDK?

Does anyone know what the situation is for Xcode 4.3 vs X11 SDK? The Xcode 4.3 installation doesn't install the Command Line Tools by default and installing Xcode 4.3 from the AppStore left the Downloads preference panel in Xcode 4.3 showing the Command Line Tools as installed. This forc

Re: xcode 4.3 breaks macports

On Jan 29, 2012, at 3:48 AM, Rainer Müller wrote: > On 2012-01-28 00:18 , James Gregurich wrote: >> I'm not sure if this is known or not, but Xcode 4.3 breaks macports. >> I'll report what I have learned in hacking my macports install into >> working. Note that /

  1   2   >