On Oct 22, 2013, at 5:05 PM, Brandon Allbery <[email protected]> wrote:

> On Tue, Oct 22, 2013 at 7:15 PM, Ryan Schmidt <[email protected]> wrote:
> On Oct 22, 2013, at 14:02, Gary Little wrote:
> > Installing from the svn trunk worked for me as well. I do also note that 
> > you have to manually install the command line tools using "xcode-select 
> > —install”.
> 
> It's good to know that the command line tools can be installed using 
> "xcode-select —install", but did the instructions in our guide for doing so 
> using the Xcode application's preferences window not work?
> 
> It's been reported that Apple removed that; they're auto-installed if you run 
> clang, or manually installed with "xcode-select --install". I just updated 
> the ProblemHotList on the wiki to reflect this and some other 10.9/Xcode 
> 5-isms.

A couple of notes:

        (1) If you have already installed Xcode 5 on Mavericks, and haven’t yet 
installed the command line tools, then running clang won’t prompt you to 
install the command line tools. This is because Mavericks has shims that thunk 
into the tools built into Xcode.

        (2) So on Mavericks, if you’ve already installed Xcode 5, I think the 
only way to trigger the install of the command line tools is through the 
xcode-select —install mechanism.

James
_______________________________________________
macports-users mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-users

Reply via email to