On 7 May, 2014, at 7:17 am, Jens Alfke < email@hidden> wrote: On May 6, 2014, at 4:11 PM, William Squires < email@hidden> wrote: I've got it to the point where I can run it in the debugger, but I can't specify the command-line arguments. So I figured I'd run it from Terminal.app, but I can't find where the executable is?!?!? It's not in the same folder as the project, nor is there a "Build" folder in there, either.
By default, recent versions of Xcode seem to stick the project build folders down inside ~/Library/Application Support/ somewhere. No idea why; it seems incredibly inconvenient and hard to find!
The default on recent versions of Xcode is to stick the project build folders in ~/Library/Developer/Xcode/DerivedData, not in ~/Library/Application Support. It's been like that for quite a while now. I personally prefer it being out of the project folder which is already plenty messy enough. The only thing I could wish for very occasionally is to have the final product, executable, library, something, copied into a custom, easy-to-remember location.
PS why couldn't the original poster specify the command-line arguments? You add them to the debug scheme. Annoying if you are changing them on every run, but if you aren't, quite easy. |