Dependency analysis failing - FIX (Re: What are your top desired improvements in Xcode ?)
Dependency analysis failing - FIX (Re: What are your top desired improvements in Xcode ?)
- Subject: Dependency analysis failing - FIX (Re: What are your top desired improvements in Xcode ?)
- From: Alex Curylo <email@hidden>
- Date: Sat, 17 Feb 2007 11:17:16 -0800
on 2/17/07 3:10 AM, email@hidden at
email@hidden wrote:
> The most nasty thing about XCODE / GCC for me!
>
> Anybody have see that if you get only a modified HEADER(s) from CVS or just
> go into some header and change some line, click BUILD and ... Nothing.
>
> This is terrible.
>
> We are forced do full rebuild so often like we NEVER did in CW or Visual.
> Taking into account "cool" speed of GCC this is not pleasant.
>
> How it is possible that compiler do not see modified header?
A workaround that's always sorted it out for me so far is to add the
offending header into the project directly. Never had a problem noticing
changes in .h files that were in the project, and never fails to notice them
once added.
If you don't feel like following the practice of adding all .h files to your
project, to find out exactly which of your headers are offending you can
follow this process:
1) Set build preference for "Unsaved Files" to "Always Save"
2) Open every .h file your source includes, and make some trivial change
like hitting space and deleting it, just enough to get the window marked
dirty.
3) Build the project.
4) All windows still unsaved are the ones that qualify as "offending". Drag
their proxy icons into your project. Build again; they will now all save and
be used by the compiler; no more problem!
Anywho, that's my experience, that wherever XCode's dependency analysis is
showing this annoying degree of independence, it affects unsaved editor
windows and compiles exactly the same way, and the easiest way to deal with
it is to just make a practice of including every single .h file the code
uses in your project, there's no obvious common reasoning behind which ones
it decides it's going to ignore.
Now, to get back to the main thread, I can't believe no one's mentioned
CodeWarrior's awesome file/folder comparison windows. You all actually think
FileMerge _doesn't_ suck compared (heh) to it, or do you use something
currently supported that I don't know about?
--
Alex Curylo -- email@hidden -- http://www.alexcurylo.com/
"I suddenly found myself writing, from scratch, an ATM
back-end that's used by a growing number of banks...
now I get nervous using ATMs." -- Greg Weston
_______________________________________________
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