Re: Is there still no way to just compile a single file?
Re: Is there still no way to just compile a single file?
- Subject: Re: Is there still no way to just compile a single file?
- From: Tom Davie <email@hidden>
- Date: Tue, 16 Jul 2013 20:41:07 +0200
On Jul 15, 2013, at 10:47 PM, Quincey Morris < email@hidden> wrote: On Jul 15, 2013, at 13:27 , Jens Alfke < email@hidden> wrote: I would say “just hit Cmd-B and look for errors”, but I know that some people are saddled with projects that take more than a few seconds to build. It's not just a time issue. There are two scenarios I know about in Xcode 4.6.3 where Build isn't such a good solution:
1. You have errors in a lot of files after a build, then you fix (say) a header that resolves the errors in some of the files. If you now try to build (to clear the errors from the issues navigator), Xcode may build files that still have un-fixed errors, and stop building (because of the errors) before it gets to the ones you did fix.
Preferences -> General -> Continue building after errors.
In all fairness, the “compile one file” solution won’t work here either – which code unit should Xcode compile if you’re editing a header?
2. You have an imported header file that imports a header file that doesn't exist, or that causes errors. Sometimes Xcode doesn't report the resulting errors in the source file that does the initial import.
Unfold the error – you’ll get a list of “in file include by x.h; in file included by y.h; in file included by z.m” Tom Davie
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden