![]() I followed the instruction on the official website ( ) plus some other guides, but I'm note an expert and I didn't reach my goal. I was wondering if someone can please help me figure it our what to do. I've had so many nightmares with it, certainly never figured out the "right" way to work with it.I've some question about uninstalling Anaconda from macOS Big Sur. You're generally correct to be concerned about removing files which might be depended upon by native apps, but it's never happened for me that software I downloaded didn't work because I hadn't yet installed the command line tools except when it was obviously a blunder on my part (see: Sublime Merge, etc). Sublime Merge won't get anywhere unless you have git installed. They'll work just fine whether or not you have the command line tools installed, unless they are specifically designed as a frontend for those tools, e.g. Neither do the vast majority of tools bundled as full apps released online. Yet, apps from the App Store don't haggle you to download some 2GB of extra dependencies, The Real Mac System Files, before running them. ![]() ![]() Remember that the command line tools are a completely optional installation (i.e. I'm not sure you're totally right about that. But that's all a hunch and I don't know for sure, you'll want to do some testing yourself to check it out. If they don't work, you can probably uninstall and reinstall the tools and they will be relinked with the newer SDKs, and then the old SDKs should be unused. If those tools still work while the folder is displaced, then it should be safe to remove and clear up some space. I don't know any specifics about them but it might be possible that tools which you installed (via Homebrew for example) on an older version of macOS might depend on the library files still contained under that older macOS SDKs folder. A (relatively) safe and easy way to check would be to move them to some other directory and reboot your system, mess around for a few days, and if everything keeps working as it's supposed to, then odds are they were just installation files only used on older versions of macOS and are safe to remove. ![]() But it should be safe to remove the ones which are behind the current version of macOS you're using. Sorry, I'm not super sure about those files. (You'll just have to wait on a pretty long software download.) If anything stops working after you remove this folder - that is, CommandLineTools and its folders SDKs, Library and usr - then you can reinstall them from the command line using the command xcode-select -install.Įdit: None of these are "junk" files because they're code library files (executable binaries and what-not) which lots of tools depend on, but if you don't use those tools, they're OK to remove, and can be easily reinstalled later. But apps you downloaded from the App Store (and most apps from other sites online) will keep working without the utilities here. If you've installed programs or tools with Homebrew before (a very popular command line tool for installing stuff, often developer utilities but lots of other software too), then those most likely depend on the stuff in these folders. It's basically a bunch of developer utilities that are essential for any UNIX or command line programming. You're in the CommandLineTools folder, which is actually OK to remove - provided you don't use any of the tools it provides.
0 Comments
Leave a Reply. |