# Try the AppleScript automation method rather than relying on manual. This short excerpt from my macOS bootstrap.sh script has been tested as of December 2021. * Command Line Tools (macOS Mojave version 10.14) for Xcode-10.1ĮDIT (2021-2022): Apple's servers now respond with a 302 Redirect to Post-apocalypt. * Command Line Tools (macOS High Sierra version 10.13) for Xcode-10.1 * Command Line Tools (macOS El Capitan version 10.11) for Xcode-8.2 * Command Line Tools (OS X 10.10) for Xcode-7.2 '')" |Ī few example results: * Command Line Tools (OS X Mavericks)-6.2 Grep "\*.*Command Line.*$(sw_vers -productVersion|awk -F. One variation that seems to work (limited testing) on 10.10-10.14 (10.9 doesn't return an osx version number in the cli tools name.so this doesn't work there): PROD=$(softwareupdate -l | Softwareupdate -l | grep "\*.*Command Line" - if this returns multiple versions, you might need more specific logic. Updates applied for compatibility with at least 10.9-10.14 touch /tmp/.-progress This worked on my 10.10 headless VM without a logged in UI. Hoping that is the line of least resistance.Wish I could claim credit for this one, but I found it buried in While I am still a hold out to the upgrade to HS, it will be only a very short time before I do this upgrade. As a bonus I like opendiff in some cases where my main tools are farther out of reach.ĮDIT: I see that Apple now provides a direct way of installed Command Lines Tools only as Command_Line_Tools_macOS_10.13_for_Xcode_9.4, but it is only for High Sierra. My main use of the CommandLineTools is to support MacPorts. The current version of Xcode is now 10GB. In many places in the threads mentioned above, people complain about having to have 6GB of unwanted code this is no longer incorrect. Xcode-select: error: tool 'opendiff' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance The result is that when full Xcode is not installed, when trying to run a command, I get the following error message or similar, depending upon the command: I have installed Xcode, uninstalled it, installed and uninstalled standalone CommandLineTools, used xcode-select -switch, and more, all in various combinations. I have gleaned a lot of steps from the following sources:Īnd likely more pages that I did not record. I have tried many variations on all the suggested steps, along with attempts at clean uninstallation and starting over. There are many discussions of similar issues, but none exactly what I am seeing.Ī short answer to my question would be "it is no longer possible to run CommandLineTools unless full Xcode is installed". Please note: this is not a development question but an installation of software question. Now I cannot get it to install correctly. In the past it used to be easy to install CommandLineTools without Xcode.
0 kommentar(er)
