Re: Problem with Rez search paths
Re: Problem with Rez search paths
- Subject: Re: Problem with Rez search paths
- From: Chris Espinosa <email@hidden>
- Date: Mon, 1 Jun 2009 10:21:03 -0700
On Jun 1, 2009, at 7:38 AM, email@hidden wrote:
I've been scratching my head over a problem that I'm having with
building a project in XCode at the moment. The whole thing builds
fine until it gets to the Rez stage. Then it fails because a header
file that is included in the .r file includes <string.h>. This in
turn includes <_types.h> (which is in the /usr/include directory)
which includes <sys/_types.h> (which is in the /usr/includes/sys
directory). Rez sees this and interprets the "sys/" as meaning a
framework called "sys" rather than a subdirectory.
Try as I might I cannot make it look for the sys/_types.h file in
the right place. Has anybody else on the list had this problem
before? Is there a Rez option that would make it work?
No good will come of importing <string.h> and its friends into Rez.
The vast majority of system headers have C/C++ constructs that Rez
will not understand. When #including header files for Rez, you should
take care to ensure that they are only Rez files or header files
shared by Rez and the compiler that contain only preprocessor
directives like #define, or are heavily conditionalized with #ifndef
rez to isolate C constructs (and include chains!) from Rez content.
The answer to your question is to set the Rez Header Search Path build
setting to /usr/include, but that's not the real answer to your
question, it'll simply give you a better and more precise error when
it tries to read /usr/include/_types and chokes on all the C. The
correct thing to do is to prevent the header file from #including
<string.h> when being included by Rez.
Chris
_______________________________________________
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