Re: BugReport: Build after changing build config compiles old code
Re: BugReport: Build after changing build config compiles old code
- Subject: Re: BugReport: Build after changing build config compiles old code
- From: Heath Raftery <email@hidden>
- Date: Tue, 27 Sep 2005 10:29:35 +1000
I've now followed this up with bugreport.apple.com as a Problem ID:
4267979
Along with the report I included a tiny project (created a Cocoa app
in Xcode and added a single NSWindowController subclass) which
exhibits the behaviour, and added this to the report:
Discovered some critical conditions while trying to reproduce this:
1. Doesn't need 2 targets. One will do.
2. Doesn't need to be Deployment/Development instead of Release/Debug.
3. Is now 100% reproducible with these steps!
a) Open the build results window. Compile both the Release and
Debug version.
b) Insert a syntax error into the MyWindowController.m file (I was
just misspelling showStuff) and Apple-S.
c) Build the current configuration. Click the failure line to
highlight the error.
d) Fix the error but *do not save*.
e) Switch to the alternate build configuration via the drop down
menu in the build results window.
f) Now save using Apple-S, and click build. Old error appears
despite being fixed in version on disk.
A similar bug can be reproduced by doing the opposite - introduce a
syntax error, switch configs, save, then build. Build succeeds when
it should not.
Regards,
Heath
On 20/09/2005, at 10:18 PM, Heath Raftery wrote:
Hey list,
I tried to file this bug using BugReporter, but got this error,
depending on which Component/Product I selected: "The default
assignee of the DTS component , version All, does not have a Radar
account. Please choose another component.". I seem to recall this
may be because I only have a student account. I'll try my luck here
instead:
Versions: Mac OS X 10.4.2 (8C46). XCode V2.1, IDE: 621.0, Core:
620.0, ToolSupport: 610.0
I have an Xcode project with two targets and often build both using
the Deployment and Development build configurations. The steps
which usually lead to the problem go like this:
1. Make some changes (with errors) to the source. Build using the
current config. Build fails.
2. Fix the errors in the source, save the files, and build again.
Build succeeds.
3. Switch immediately to the other build configuration (in the
Build window) and build again.
4. Build fails due to old errors in source! Clicking the error
shows the corrected source file, at the location of the old error.
5. Build again without doing anything else and build succeeds.
Since I save changes to a source file, I'd like Xcode to compile
the version on disk, regardless of the configuration I choose. The
workaround is annoying but workable - what would be unacceptable is
when the fixed errors in the source do not result in compile
errors, and Xcode produces a build based on old code.
Regards,
Heath
_______________________________________________
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