Re: Xcode 3 Recursive paths going missing
Re: Xcode 3 Recursive paths going missing
- Subject: Re: Xcode 3 Recursive paths going missing
- From: Rick Ballard <email@hidden>
- Date: Mon, 29 Oct 2007 17:08:09 -0700
Hi Matt,
Would you mind filing a bug report at bugreport.apple.com, including
your build transcript that demonstrates the problem? It's possible
that this is a duplicate of a known issue, but the similar known issue
does reproduce on Xcode 2.4.1, whereas you've indicated that this
problem does not. Even if the bug does get returned to you as a
duplicate, we'll still be tracking the information you provide.
Unfortunately, we do not have a workaround to recommend at this time,
short of discontinuing use of recursive search paths in this situation.
Thanks,
- Rick
On Oct 29, 2007, at 6:17 AM, email@hidden wrote:
I have a large project which uses the following for its
USER_HEADER_SEARCH_PATHS:
(spaces replaced by new lines here to simplify reading)
USER_HEADER_SEARCH_PATHS =
../../**
../../..
../../../..
../../../Common/**
../../../../../../common/dev
../../../../../../model/dev/**
../../../../../../GUIComponents/dev/**
../../../../../../customfluid/dev
../../../../../../../common/dev
../../../../../../../../common/guicommon/dev/pp/proj/xcode
../../../../../../../../common/EPS_Mo/dev
../../../../../../../../common/guicommon/dev/common/inc
../../../../../../../../common/guicommon/dev/pp/pputil/inc
../../../../../../../../common/paintlib/dev/**
../../../../../../../../common/ags/dev
../../../../../../../../common/corbaprop/dev
../../../../../../../../common/fluid/dev
../../../../../../../../common/apple/core/dev/**
In Xcode 2.4.1 on Tiger and 2.5 on Leopard these get properly
expanded out as necessary.
However, with Xcode 3, it usually stop generating any more -iquote
or -I paths after either:
../../../../../../model/dev/**
or sometimes:
../../../../../../GUIComponents/dev/**
As such, lots of our source fails to compile since the compiler
can't find the necessary headers.
Sometimes, (and I have no idea what is different) the full set of
paths does indeed get fully resolved and the build will succeed.
However this is definitely the exception and not the norm.
Before I go to the (quite considerable) trouble of manually turning
USER_HEADER_SEARCH_PATHS into a fully resolved non-recursive set of
paths, I wanted to find out if this was a known issue and if there
is any other workaround that will allow me to still use the
recursive paths.
Matt Gough
Agfa Graphics
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@apple.com
This email sent to email@hidden
_______________________________________________
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