xcode-select -switch path when using cli toolkit
Asked Answered
N

5

49

With the release of Apple's Command Line Toolkit for Xcode, I am trying to avoid needing to install Xcode proper. In order to do this, I need to set the path to xcode for specific make files that depend on the xcode-select path (which is currently pointing to /Developer)

Where do I point the xcode-select path when using the CLI Toolkit for Xcode?

If I install Xcode, it's just /Applications/Xcode.app, but I don't know where the CLI Toolkit is being placed.

Thanks.

UPDATE:

It appears from the pkg installer that it dumps it all to /usr/bin and then xcode-select or other scripts internal to the pkg create the paths for xcodebuilder etc. Can anyone confirm?

Nide answered 28/2, 2012 at 7:16 Comment(0)
S
99
sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer
Swansdown answered 13/3, 2012 at 7:14 Comment(7)
is this the case if I haven't installed Xcode.app? Or does the CLI Toolkit install to Xcode.app?Nide
Try this: github.com/kennethreitz/osx-gcc-installer if your only need gcc or etc.Swansdown
you save me! mac ports suggests to run sudo xcode-select -switch /Applications/Xcode.app which makes no sense :(Exuviae
so i still want to know, does the xcodebuild tool get installed to /Applications/Xcode.app if I dont install Xcode. It doesnt seem to make sense that it would.Nide
This may be obvious, but if you have installed XCode Beta version you need to run sudo xcode-select -switch /Applications/Xcode-Beta.app/Contents/Developer instead.Footy
Your answer is loook same as https://mcmap.net/q/187133/-xcode-stops-working-after-set-quot-xcode-select-switch-quot this answerAloft
@Exuviae You don't need to use the path to Developer. Just setting the path as mac ports indicates also works.Belletrist
A
33

I installed the CLI tools only (e.g. no Xcode) and received an error with a native gem extension build:

xcode-select: Error: No Xcode is selected. Use xcode-select -switch <path-to-xcode>, or see the xcode-select manpage (man xcode-select) for further information.

After looking at this and browsing the directories, it appears the BSD tools got installed in /usr/bin therefore:

sudo xcode-select -switch /

seems to work.

Aorta answered 16/9, 2012 at 2:41 Comment(2)
Worked for me using MacOs Lion version and the Xcode CLI dpk installer. Thanks!Immorality
if you run: "$ sudo xcode-select -p" it will show: /Library/Developer/CommandLineToolsFerrin
I
19

Just did this today after removing Xcode to reclaim HD space. I used:

sudo xcode-select -s /Library/Developer/CommandLineTools
Imprudent answered 7/6, 2019 at 12:42 Comment(0)
N
7

I encountered this problem recently because I had several XCode versions installed on the same machine. If you have one or more XCode previously installed, you can simply reset the path with the command:

sudo xcode-select -r

This will reset the path to the default, which is /Library/Developer/CommandLineTools.

Novelia answered 26/7, 2021 at 19:23 Comment(0)
M
1

For my setup (Xcode 4.0.2 on 10.6.8), I used spotlight to search for 'xcodebuild' to find where the Xcode CLI tools actually live.

The CLI tools are in /Developer/usr/bin, so my xcode-select command looks like (the /usr/bin is appended by xcode-select):

sudo xcode-select -switch /Developer
Miscarriage answered 21/5, 2012 at 20:24 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.