Re: Xcode does not resolve file-dependencies correctly (was: Re: crashes after changing signatures of virtual functions / virtual inherited classes)
Re: Xcode does not resolve file-dependencies correctly (was: Re: crashes after changing signatures of virtual functions / virtual inherited classes)
- Subject: Re: Xcode does not resolve file-dependencies correctly (was: Re: crashes after changing signatures of virtual functions / virtual inherited classes)
- From: Steve Checkoway <email@hidden>
- Date: Fri, 4 Aug 2006 04:04:44 -0700
On Aug 4, 2006, at 3:09 AM, Stephan Huber wrote:
In my files I use for the #includes something like this:
#include "Application/Component1/File1.h"
This is not an absolute path. An absolute path would start with a /.
As long as src (in your case) is in your search paths, this should be
looking for the file src/Application/Component1/File1.h.
Say I have the following dependency-chain:
main.cpp -> File3.h -> File1.h
If I change something on File1.h, Xcode sometimes refuses to
compile main.cpp, or File3.cpp and I think this leads to multiple
class definitions because of the heavy usage of templates, which
uses classes defined in File1.h as parameters for other templates.
I assume you mean that main.cpp is including File3.h which is
including File1.h. Are the header files in your project? I'm not
positive this makes a difference but there was a recent thread "stop
new headers from being added to copy files?" which, I believe,
mentioned that certain operations fail if header files are not
referenced in the project apart from #include. It's possible this
affects dependency checking.
--
Steve Checkoway
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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