![]() Applications/Xcode.app/Contents/DeveloperĬonfigured with: -prefix=/Applications/Xcode.app/Contents/Developer/usr -with-gxx-include-dir=/usr/include/c++/4.2.1Īpple LLVM version 6.1.0 (clang-602.0.49) (based on LLVM 3.6.0svn)Īpple LLVM version 6.1.0 (clang-602.0.49) (based on LLVM 3.6. I'm answering against the more recent version (where the tools actually are in the Xcode.app pkg), but I'm pretty sure that if the path & output returned by xcode-select -p, gcc -v, and llvm-gcc -v/clang -v are harmonious then they should be the same, i.e. So when you know for sure the commandline tools are installed (because, for instance, xcode-select -install tells you so) but none of the other methods works, check softwareupdate -history!įor modern versions of xcode the command xcode-select -version will display the version number of command line tools, whether or not Xcode.app is installed. Display Name Version DateĬommand Line Tools for Xcode 12.1, 22:38:33Ĭommand Line Tools for Xcode 12.3, 16:38:27 Which listed 12.3 as the last version it updated. You can download the Xcode command-line tools in either of two ways: To install the necessary Xcode tools using Xcode on the Mac: Start Xcode on the Mac. How I finally found out what version of the XCode Commandline Tools is installed I stumbled upon the command: softwareupdate -history However I knew that my version must be out of date as the installer for one of homebrew packages told me so! Softwareupdate -list told me everything was up to date. Xcode-select -version only gave me the version of xcode-select itself, with no clue as to the commandline tools version. Not having XCode installed (and having no need for it), I could not look in settings dialogs of that either. ![]() ![]() pkgutil didn't give me the package of the XCode Commandline Tools, with none of the suggested package names. None of the available answers to get the version worked. I had XCode Commandline Tools installed for sure, but not XCode itself. I also tried reverting to the previous veresion by downloading and installing XCode command line tools 14.3, but then even more problems were found that many tools/libs were referring to MacOSX13.3.sdk instead of MacOSX13.1.sdk and reinstalling them didn't help.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |