Not always compiling modified files?

Subject: Not always compiling modified files?

From: Jonathan Taylor <email@hidden>

Date: Fri, 18 Nov 2005 11:39:50 +0000

Delivered-to: email@hidden

Has anyone seen problems with Xcode not always compiling dirty files? I can't seem to come up with a repro scenario, but sometimes there is no question that the following sequence goes wrong:

1. Modify a file in the project (using the Xcode editor) with the debug configuration active.

2. Possibly build and debug the file (I'm not sure to be honest)

3. Switch to release configuration

4. Press "build and run"

Sometimes (not by any means always) no building occurs and the _old_ version of the executable is run. Normally this is pretty obvious as it then displays a bug that I've already fixed or something, but it's sometimes pretty confusing, as you can imagine!

In this scenario, stopping the program and clicking "Build" causes the program to be build correctly. It seems to be very specifically related to switching build configuration just before the "build and run". The only plausible suggestion I can come up with as to why this happens is that it might be something to do with a window condition where the compile-in-the-background feature gets confused by a switch in configuration, but even that seems a pretty unlikely guess.

I seem to remember this was a problem with Xcode some time back, but I thought it had been fixed. Does anyone else still see this with 2.2? And can anybody point out a magic workaround (other than realising what has happened and explicitly selecting "Build")? I don't really feel it would be much help to raise a bug against this as it's so vague and unreproducible...

Cheers

Jonny

_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/xcode-users/email@hidden This email sent to email@hidden