Re: Xcode dependency handling
Re: Xcode dependency handling
- Subject: Re: Xcode dependency handling
- From: Jim Wintermyre <email@hidden>
- Date: Mon, 5 Feb 2007 16:05:40 -0800
Title: Re: Xcode dependency handling
> I open 'headerThatIsNotSaved.h' and
make a small change, do not
> manually save, icon is dark
(correctly).
>
> Build.
>
> All dependencies are checked,
environment variables setup spools in
> build window, and nothing else.
Build succeeded in result window.
This is expected behavior. Unlike
CodeWarrior, Xcode builds with the
contents of the saved files on disk, not
the contents of unsaved
files in windows.
Personally I really wish Xcode had a preference to behave like CW
does. A lot of times I want to make a minor change and just test
it out immediately, but I don't want to save the file because if the
change works I'm going to go back and re-code it the "right"
way... and if it doesn't work then I just don't save the file.
But now that I've saved the file, CVS thinks it's modified, and even
if I back out the change the "quick" modified check thinks
the file is modified, so I have to then get a clean copy from
CVS.
A header does not need to be a project
member in order to be indexed,
searched, or included in a compile; the
dependency mechanisms and the
search paths will cover all included
headers, whether listed in the
project or not.
This is not true in the case of indexing headers, at least those
that are included via a recursive header search path. If the
headers are not specifically added to the project, indexing symbols
defined in the headers doesn't work properly. I filed a bug
report on this long ago (rdar://problem/4423470).
Jim
_______________________________________________
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