Ya, I have SO many problems with Xcode, I tend to live in a "recompile the universe" world, when I'm "scripting" builds, just to be safe. The extra compile time is slightly painful, not enough for me to expend extra effort to alleviate the pain tho. The most recent Xcode's do seem to be better about noticing updates. And, it does tend to be an edge case scenario - adding or removing a file.
It's probably true that a regular build would be fine, most of the time, if we provide some kind of option to do a "full" build, just in case. Perhaps the job of a "clean" script, or something. On Mon, Oct 15, 2012 at 11:00 PM, Shazron <shaz...@gmail.com> wrote: > > on iOS - why do a clean build instead of a regular build? > > This was because in some cases an updated file was not copied over, or > a built app still had an older file that was removed from the project. > An edge case to be sure, but if there was a script that referred to > the old file still, it might generate undesired results. It might have > happened in an older version of Xcode, so I'm not sure if it still > occurs. > -- Patrick Mueller http://muellerware.org
