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.
In addition, at least sometimes when there are multiple files with errors, Xcode won't live-compile or index anything, presumably because it tries to re-analyze the ones that still have errors, and gives up after trying a few of them.
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.
Steve's point is that (a) you don't know for sure if or when the file you're looking at has been live-checked; and (b) Build isn't a great way to make sure. I agree with him on those points.
Note that Xcode versions earlier than 4.6 were a lot worse about abandoning live compilation mysteriously. Also, I haven't looked at Xcode 5 to see if it's any better.
|