AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Xcode command line tools install9/5/2023 For people running the latest version of Catalina (10.15.2 at the time of this writing), this has worked when the other two solutions haven't. With the much smaller Xcode Command Line Tools via manual download.With the much smaller Xcode Command Line Tools via xcode-select -install.With the full Xcode (~7.6 GB download) from the App Store app.People running Catalina have had success with some but not others in a way that has been unpredictable. There are three ways to install the Xcode libraries node-gyp needs on macOS. If test failed, there is a problem with your Xcode Command Line Tools installation. If test succeeded, you are done! You should be ready to install node-gyp. Let's first make sure that your Mac is running Catalina: Fixing Catalina for older versions of node-gyp Is my Mac running macOS Catalina? Use npm config delete node_gyp to unset this configuration option. If you use npm config set to change your global node_gyp you are responsible for keeping it up to date and can't rely on npm to give you a newer version when available. usr/local/lib/node_modules/node-gyp/bin/node-gyp.js). usr/local/bin/node-gyp), or a path to the node-gyp installation directory and the bin/node-gyp.js file within it (e.g. Where "path to node-gyp" is to the node-gyp executable which may be a symlink in your global bin directory (e.g. run npm with an environment variable prefix: npm_config_node_gyp= npm install.through npm install), you will have to install node-gyp (either globally with -g or to a predictable location) and tell npm where the new version is. If you need to use node-gyp from within npm (e.g. If you are using node-gyp directly then you should be able to install v7 and use it as-is. The newest release of node-gyp should solve this problem. 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.Gyp: No Xcode or CLT version detected! node-gyp v7 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. 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.
0 Comments
Read More
Leave a Reply. |