Re: Files still dirty after build
Re: Files still dirty after build
- Subject: Re: Files still dirty after build
- From: Carl Norum <email@hidden>
- Date: Wed, 29 Sep 2004 16:14:39 -0600
Just add the appropriate include paths to your build settings.... that
should make things work correctly. It would be nice if XCode noticed
such things on its own I suppose, but I'm sure you can come up with
scenarios where you wouldn't like that behaviour just as much.
-- Carl
On Sep 29, 2004, at 4:05 PM, Trygve Inda wrote:
Regardless of whether this arrangement is normal practice or not, the
build behavior is still clearly either an Xcode bug or something
messed
up in this project. It should make no difference where you put your
source files relative to your headers as long as the Xcode can find
them.
I tried just making a simple project, adding source & headers
directories to the project, and using File->New File... to make a new
.c file, and then a new .h file in the respective directories. The
build system did what it should, and only rebuilt the source file when
something had actually changed. So there's a little more going on
than
just sources in one directory, headers in another...
I don't mean the files arranged like this in the Xcode project
(although
they are), but it breaks when the files are like this on the hard
drive.
Trygve, if you can reduce your project to some small example that
shows
this happening, please file a bug with the project.
I did some more testing....
If my files are arranged (on the HD) like
Project/header/myapp.h
Project/source/myapp.c
If I use #include "myapp.h" it stays dirty after a rebuild
If I use #include "../header/myapp.h" all is well. I don't think I
should
have to specify where exactly it is since the IDE knows.
It seems to only be an issue when the headers are in a path that is
"upstream" from the .c.
I have always arranged my files this way as it just seems to make
sense, but
Xcode sure doesn't care for it.
Trygve
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
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