I had to do this for subsequent Ventura updates as the dropdown above didn’t give any newer versions. Update: Thanks to Abdallah Abedraba for pointing out that you can also get the command line tools from. I clicked the dropdown menu, selected what you see there, and now Homebrew is happy. Where it now shows the Command Line Tools was previously empty. Not sure what else to do, and remembering that in the past I’ve downloaded the Command Line Tools from Xcode itself I started going through the settings page. Another command I have tried is: xcode-select -install but that tried to install and threw an error. This Apple account will be needed for Xcode download later. It’s important to remember: when configuring macOS, you should enter a valid Apple ID. Step 3: Then, install macOS and boot your VM. How do I get the Command Line Tools though? In the past I’ve downloaded that from the same website, but I couldn’t find anything there. Choose two CPUs in the Processor tab Increase the video memory above 128MB in the Display tab. So far so good, this even quiets the first Homebrew warning. This downloads a large zip file from which I can extract Xcode-beta. Simply delete the existing Xcode and download the latest from Apple. This will make Homebrew install formulae and casks from the homebrew/core and homebrew/cask taps using local checkouts of these repositories instead of Homebrew’s API. Not a problem, I’ve been down this path before. It didn’t show any updates there, and if I try to open Xcode from the App Store it refuses to open and gives some error message about me having XCode 13.4.1 and I should get the latest version XCode 13.4.1 instead (clearly a bug in the messaging). I had Xcode 13.4.1 installed from the App Store. Xcrun : error : invalid active developer path ( / Library / Developer / CommandLineTools ), missing xcrun at : / Library / Developer / CommandLineTools / usr / bin / xcrun
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |