Re: Header search path with XCode 2.1
Re: Header search path with XCode 2.1
- Subject: Re: Header search path with XCode 2.1
- From: "E. Wing" <email@hidden>
- Date: Tue, 5 Jul 2005 11:43:03 -0700
> From: Andrew Hannon <email@hidden>
> Date: Sat, 2 Jul 2005 18:54:00 -0400
>
> The folder that contains the project is a directory resembling ~/
> Documents/CVS/{Project}. I have several folders in the CVS/
> directory. I use -I../ to access the header files in these different
> folders. However, while this worked as I expected in XCode 2.0, XCode
> 2.1 refuses to acknowledge the flag (even though I have filled out
> the appropriate "Header Search Paths" field with "../"). Oh the
> frustration! As a sanity check, I manually added "../" to the first
> offending #include violator, and of it compiled.
>
> Has anyone seen this? I've read other's accounts of XCode 2.1
> seemingly ignoring user specified parameters. Can anyone help, as I
> am quite frustrated at the moment!
>
> Thanks,
>
> Andrew Hannon
I don't know if you've solved this by now, but I think I've had a
similar problem with Xcode 2.1. Xcode will not find any of my header
files in my 3rd party frameworks which are installed in
/Library/Frameworks. If I have code like #include <osg/Node>, Xcode
2.1 cannot find these headers, even if I explicitly add
/Library/Frameworks to the header search path. This was not a problem
in prior versions of Xcode.
I did discover that I only have this problem if I enable the 10.4
Universal SDK target for the project. If I leave the SDK option on
Current Mac OS, Xcode finds my header files. If you switched to 10.4
Universal SDK, you might want to undo that.
I filed a bug report on the 29th. It is bug #4165982. It has been
marked as duplicate. If this turns out to be your problem too, I
recommend you file another bug report to vote for the problem to be
fixed.
-Eric
_______________________________________________
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