Source trees buggy?
Source trees buggy?
- Subject: Source trees buggy?
- From: "Blair M. Burtan" <email@hidden>
- Date: Sun, 22 Oct 2006 20:54:28 -0700
I'm having a hell of a time getting Xcode 2.4 source trees to work
everywhere. I've noticed a few things that don't make sense to me.
Let's say I have the following source tree set up:
Sources Sources /Development/My Application/Sources
Where /Development/My Application/Sources has a sub-directory "include"
I though you could add the following to the User Headers search paths:
$(Sources)/include
But for some reason Xcode (or GCC) can't find any of the #includes e.g.
#include "test.h"
Seems like I have to actually add the #included .h files to the project for
GCC to find them.
Then there's the issue of User headers versus system (non-user) headers.
I'm running into the problem of GCC not being able to find #include
<somefile.h> if I use a source tree search path.
Are these bugs? Why aren't the correct usage of source trees in Xcode
projects not completely documented?
And how about Xcode verifying that a source tree is valid before you drive
yourself crazy because you typed it in wrong?
Blair M. Burtan
Northern Lights Productions
www.northernlights3D.com
_______________________________________________
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