On 30.04.2005, at 09:36, Dair Grant wrote:
Hi,
It appears that in Xcode 2.0, as per previous versions, switching the
active style does not mark object code as being out of date.
This makes it very easy to produce a bad binary when using build styles;
unless you remember to do a "clean all" every time you switch, you end
up linking together code built with multiple styles.
I've never logged a bug against it as I assumed it would have to be
fixed at some point - ideally by saving distinct object code for each
style, worst-case by forcing a clean all after a switch.
But since it's still there, is this behaviour actually useful in some
situations?
I think it is a bug, according to the documentation to XCode 1.x:
In "Analyzing Build Dependencies" it says:
"While each build phase defines a set of inputs and a task to perform on those inputs, the order in which the individual operations associated with that task are performed is determined by the graph of the target’s file-level dependencies. Xcode tracks the current build state of each target, maintaining project information that affects the build state of the target, such as the active build style. For native targets, Xcode also maintains:
▪ A graph of the target’s file-level dependencies
▪ A queue of nodes that require updating"
-dair
___________________________________________________
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Help/Unsubscribe/Update your Subscription:
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Help/Unsubscribe/Update your Subscription:
