Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Trashing the folder does not properly uninstall Xcode.</p> <p>Here are the steps to uninstall Xcode from the PDF readme distributed with the installer:</p> <blockquote> <p><strong>Uninstalling Xcode Developer Tools</strong></p> <p>To uninstall Xcode developer tools on the boot volume along with the directory, from a Terminal window type:</p> <p><code>$ sudo &lt;Xcode&gt;/Library/uninstall-devtools -mode=all</code></p> <p>To remove the underlying developer content on the boot volume, but leave the directory and supporting files untouched, from a Terminal window type:</p> <p><code>$ sudo &lt;Xcode&gt;/Library/uninstall-devtools --mode=systemsupport</code></p> <p>To just remove the UNIX development support on the boot volume, but leave the directory and supporting files untouched, from a Terminal window type:</p> <p><code>$ sudo &lt;Xcode&gt;/Library/uninstall-devtools --mode=unixdev</code></p> <p>Finally, to just uninstall the directory you can simply drag it to the trash, or from a Terminal window type:</p> <p><code>$ sudo &lt;Xcode&gt;/Library/uninstall-devtools --mode=xcodedir</code></p> <p><strong>NOTE:</strong> The uninstaller that ships with previous versions of the Xcode developer tools will not clean everything off of your system properly. You should use the one installed with these Xcode developer tools.</p> </blockquote> <p>My gut feeling tells me that this process will properly nuke/replace dylibs like the one that is causing you trouble. At the very least, all trying this will cost you is time.</p> <hr>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload