Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Don't keep your projects in /Developer. That's owned by Xcode, and if you're not careful you might end up deleting everything when you install an update. Make your own directory for your code, and it will work.</p> <p>You mentioned that you don't want to move your projects because you fear broken file references. In most cases, that shouldn't be a problem, as file references are by default relative. Occasionally you'll find an absolute path in there, but it's easy to fix the broken reference—the file will be highlighted in red, so just select the file, open the File Inspector pane, and click the little Finder Window button next to the filename. You'll be able to select the new location. This even works for multiple missing files; just select the whole group of them, then click the Finder Window button to select the folder containing the missing files.</p> <p><img src="https://i.stack.imgur.com/aEH7c.png" alt="an image showing the Finder Window button"> <code>&lt;--</code> This is the Finder Window button I'm talking about.</p> <p>Once you do that, the missing file references will be resolved. I'd argue that moving your projects would be good for this purpose alone—it will help you clean up all those absolute paths that you intended to be relative.</p> <p>If you don't want to play by those rules, then you'll just have to live without refactoring. Sorry; that's just the way it is. The Developer folder is intended to hold the developer tools, not your own code. There are uninstallation scripts within the /Developer folder that will delete the entire folder. It's really not a good place for your own code.</p>
 

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