![]() The paths of Xcode and the developer tools are cached on disk in a database file named xcrun_db located in your $TMPDIR. When you attempt to run one of the developer tools, the _xcselect_invoke_xcrun function must look up the actual path of the tool. Applications/Xcode.app/Contents/Developer/usr/bin/git Is your head spinning yet? The actual tools are inside the Xcode app bundle: $ xcrun -find git By the way, if you're looking for /usr/lib/libxcselect.dylib on disk you may not find it, because Big Sur. The /usr/bin/git executable on macOS is just a stub that calls the _xcselect_invoke_xcrun function in the /usr/lib/libxcselect.dylib library, which you can see by using the /usr/bin/otool command-line tool - which coincidentally is also just a stub that calls the _xcselect_invoke_xcrun function. So I tried rebooting again, and then the issue occurred again!įor the impatient who don't care to hear the story of how I discovered the cause, I'll cut to the chase. Puzzled, I could only think of one thing out of the ordinary: I had just rebooted my Mac. Indeed it was instantaneous the next time I ran it on the same repository. This was highly unusual, as git status is mostly instantaneous for me. I ran git status on a newly created, very small repository, but the command took more than 10 seconds to finish.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |