Re: wchar link problems building for jaguar
Re: wchar link problems building for jaguar
- Subject: Re: wchar link problems building for jaguar
- From: Marquis Logan <email@hidden>
- Date: Wed, 05 Nov 2003 11:16:56 -0800
this is the same problem i had. i'm building now, hopefully this solution will help :-).
you can add those header paths to the search paths for the buildstyles of the project group itself, and that should take affect for all targets.
nibs
On Wednesday, November 05, 2003, at 10:10AM, Rob Barris <email@hidden> wrote:
>> In a nutshell, there seems to be a problem with the way Xcode sets up
>> include paths when you're doing cross-development builds, such that
>> some important C++ headers (notably c++config.h) are read from the
>> Panther /usr/include tree instead of the SDK's. You can fix this by
>> adding the following to your target's Header Search Paths build
>> settings:
>>
>> /usr/include/gcc/darwin/3.3/c++
>> /usr/include/gcc/darwin/3.3/c++/ppc-darwin /usr/include/gcc/darwin/3.3
>
>
>
> Our Xcode project has 49 targets (individually built static libs).
>
> What's the shortest route to getting the right paths activated across
>all the targets other than pasting the characters above into all of
>them?
>
> Can I set up some kind of global environment variable/value that can
>then be referenced in all the targets?
>
> Will a future Xcode release deal with this more cleanly (ie is it
>considered a bug yet?)
>
>Rob
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.