Re: Problem with Header Search Paths at Project level.
Re: Problem with Header Search Paths at Project level.
- Subject: Re: Problem with Header Search Paths at Project level.
- From: Scott Tooker <email@hidden>
- Date: Mon, 31 Oct 2005 11:04:49 -0800
On Oct 28, 2005, at 1:55 AM, Andreas Grosam wrote:
On 27.10.2005, at 20:16, Scott Tooker wrote:
On Oct 27, 2005, at 10:09 AM, William H. Schultz wrote:
Ah, but there is a way to indiciate that you want to modify the
project level setting at the target level.
The macros "$(value)" (and yes, that's literally "value")
represents the previously define value of the build setting.
For example, if at the project level I set:
HEADER_SEARCH_PATHS = /foo/bar
and then at the target level I set
HEADER_SEARCH_PATHS = $(value) bar/baz
then when I build I get:
HEADER_SEARCH_PATHS = /foo/bar bar/baz
Note that the $(value) macros can go anywhere in the build setting
so I can just as easily prepend a search path or append and
prepend paths and so on.
I previously used to use:
Project-settings:
HEADER_SERCH_PATH = /foo/bar
and then in the target setting:
HEADER_SERCH_PATH = $(HEADER_SEARCH_PATH) /bar/baz
It seemed to work. Is this really working or just by accident?
Is the "$(value)" method the recommended way?
Either way will work, but $(value) is a little bit easier since you
don't need to know the actual raw build setting name.
Scott
Regards
Andreas
Scott
Hank Schultz
Cedrus Corporation
http://www.cedrus.com/
On Oct 27, 2005, at 6:11 AM, email@hidden wrote:
Hi,
this morning I added a local include path into my XCode project
via the project info's build configuration. I found that the
#include lines I had were never being found.
I added
/usr/local/include/exiv2
into the
Header Search Paths
option for the entire project (i.e. click project icon, hit
Apple-I, click build tab, specify path for 'Header Search Paths').
when looking at the compiler output, these headers we're NOT
being included in the compilation. This is obviously why the
compiler was returning errors trying to include the files. But
I had thought this was the entire PURPOSE of the 'Header Search
Paths' option. I've checked this for both debug and release, to
ensure I wasn't deing silly and setting one config but then
using the other...
Then I changed the Header Search Paths for just the single
compilation unit, in this case a .mm file - and it works without
issues.
So why is XCode not using my additional 'Header Search Paths'
option, when I specify an additional dir at the project level
Has anyone else come across this?
John Clayton
---------------------------------
UBS AG
Information Technology
Europastrasse 2, Opfikon
Tel. +41-1-239 23 36
#claytojo
Visit our website at http://www.ubs.com
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender
therefore
does not accept liability for any errors or omissions in the
contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any
securities or
related financial instruments.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40cedrus.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:
40apple.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:
40onlinehome.de
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
_______________________________________________
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