I use my Mac for S/W development and use git as my version control tool. I have never wanted/needed X-code in the past so never installed it. I recently upgraded to Mojave and noticed my git no longer works. The error "missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun" appears, and is easily googled with a recommendation of running "xcode-select --install". When I do that, I get the pop-up offering to install the command line tools with options: get Xcode, Not now, and install. I choose install and then get the "Can't install the software because it is not currently available from the Software Update Server". Once again something easily googled. Unfortunately it seems all the recommendations center around installing Xcode which I really don't want to do. Is there a solution to this that doesn't involve loading the entire Xcode application? I'm ok with just the CLI, but would like to avoid Xcode if possible. Appreciate any suggestions.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS Mojave broke git
- Thread starter GeoffWillis
- Start date
- Sort by reaction score
Indeed, the Mojave Xcode Command Line tools are now here: (login required) Command Line Tools (macOS 10.14) for Xcode 10.1.dmg
Why not? It's free. Do you develop Mac "S/W" that doesn't require resources like images and .xib files? A full-featured Mac Application requires a lot of things like code signing and sandboxing that are handled automatically by XCode. Do you use Cocoa?
Xcode uses a lot of disk space. There's no sense in installing it if one doesn't need the rest of the features.
On my iMac the complete installation of XCode 10.1 requires 7.19 GB. A typical hard drive today is at least a terabyte. This means that it uses about .7% of a terabyte hard drive.
You didn't answer the question: What "s/w" do you develop that doesn't use any of the features of XCode - like a resource editor/compiler, debugger, etc.?
You didn't answer the question: What "s/w" do you develop that doesn't use any of the features of XCode - like a resource editor/compiler, debugger, etc.?
I'm not the person who asked the original question. Apple sells a lot of computers with expensive SSDs in them and 1TB of storage isn't that common in Mac portables. Xcode is complete overkill to write and compile command line binaries, for instance. What the OP is doing doesn't really matter; I'm sure they know what they need. I'm not sure why that matters to you.
Which git is actually running when you run git? If you're using shell cmds, enter type git or which git in the shell to have it tell you the git it's running.
If you're running git from somewhere other than a shell, please tell us how you're running it.
When you used git before, where was it running from? Is that the same as the output of which git?
The reason I've asked those questions is because Mojave may have done a few different things to break git. It may also have done something I haven't listed.
First, Mojave may have put a 'git' command into a dir in the PATH that's earlier in the search order than where you placed your git.
Second, it may have added a dir to the PATH that results in a different git than the one you were using before. This is effectively the same as the "First" possibility immediately above, but there are two distinct possible causes.
Third, Mojave could have installed some system libraries or frameworks that are no longer compatible with your original git, so even though your original git is being found and run, its reliance on a lib or framework has been damaged.
Finally, what happens if you change your PATH so your original git gets found and run before whatever git Mojave is running by default?
I was trying to avoid arguments as to the utility of XCode, simply my choice. I use Netbeans, Vis Code, Eclipse, etc and don't want/need the bloat associated with XCode. My code is not mac specific and must run on any box.
I hear that. I've got Xcode for the occasional project I may want to look at, but it is a beast that I would prefer not to mess with if at all possible. The command line tools are the best parts, and 190MB vs 13.5GB is pretty much a no-brainer.
- I run git from the command line (vi is my favorite editor...). A "which git" shows usr/bin which is in my PATH right after current dir ("."), i.e. (.:/usr/local/bin:yada yada yada) in my .bash_profile.
- There is an Anaconda dir in my path following the /usr/bin which could be issue #2 you mentioned above, but all worked fine before Mojave.
- Your #3 above has me trying to remember if I even installed git on this box, or it came loaded, I just don't remember, but the dates on most of usr/bin dir indicate it came pre-loaded.
- Not sure I follow your #4, since /usr/bin is the second thing in my PATH (echo $PATH), and which git shows /usr/bin I'd think that resolves correctly. I did try executing using full path i.e. /usr/bin/git update but no joy.
[doublepost=1541536053][/doublepost]
Thanks, you put that much better than I. I simply don't want to use it, nor defend my decision not to.
[doublepost=1541537739][/doublepost]
This solved the problem. Not sure why I had to install 970MB of CLI to get git to work, but this did the trick. Thanks to all who weighed in. Off to go commit my work before I loose it!
Last edited:
I agree with this. Xcode is my least favorite part of macOS. Even the command line tools are large when all I need is git, make, and a compiler.
You must have installed a copy of git using something other than Apple's developer tools installers. Apple puts it in /usr/bin/git, even on Mojave.