![]() 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. 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. 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. 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. And also thanks to Russ Bishop for telling Olivier about this.Xcrun : error : invalid active developer path ( / Library / Developer / CommandLineTools ), missing xcrun at : / Library / Developer / CommandLineTools / usr / bin / xcrun Update: This worked for me on macOS Sierra 10.12.1. This will remove XCode from the installed applications list of your Mac's App Store. EDIT: after some more back-and-forth I managed to get the Command Line Tools working via xcode-select -install. (Thanks to Olivier Halligon for telling me about this feature. Right click on Xcode on the right pane and select delete. xcode-select -install behaves similarly to the Mac App Store (namely claiming the tools are already installed or producing a non-working installation if I remove the CommandLineTools directories in the different Libraries). Of course, if you need space now you'll still need to go in and manually delete Device Support files that you no longer need but this feature should certainly put a cap on the number of old Device Support files that are kept around. Learn the basics of Xcode, SwiftUI, and UIKit to create apps for iOS. I think it's really cool that Xcode and macOS can now actively help you reclaim disk space by removing unused Device Support files. Get started using Xcode and the developer tools needed to build an app. The system has full control over when exactly this cleanup takes place and the exact cleanup times are dependent on variables like system activity, available disk space, whether you're connected to power and more. This means that macOS can automatically clean up old Device Support files after they haven't been used for 180 days. Any Device Support files that haven't been used for 180 days or more are automatically made elligible for deletion by the system. Pretty good, right? Xcode 12 automatically helps cleaning up Device Support filesĪ very cool feature of Xcode 12 is that Xcode will track the device / iOS version combinations that you use and update the mtime for each item in the Device Support directory accordingly. So that's 15Gb of space after about 8 months of use. When I ran these commands on a machine that got a clean install when macOS Catalina came out I was able to free up 15Gb of disk space. Clean up unavailable simulators using by typing xcrun simctl delete unavailable in your Terminal.Do the same with open ~/Library/Developer/Xcode/watchOS\ DeviceSupport.Delete folders for iOS versions that you no longer need to support.Go to your Terminal and type open ~/Library/Developer/Xcode/iOS\ DeviceSupport.To clean these files up you can do the following:
0 Comments
Leave a Reply. |