Re: Using target specific include paths

Subject: Re: Using target specific include paths

From: Mike Collier <email@hidden>

Date: Fri, 25 Sep 2009 15:36:49 -0700

Delivered-to: email@hidden

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:message-id:references:to :x-mailer; bh=uxwG682ES2Vyt/z5uEeHzOMGMFllHXNQRPhRnyi7vVU=; b=f6wzDB5UpVzA3lLhf3E3sslzD+lWjGd17nCoetx3wzYD1N56c9+JqGLuiV0UkdneH2 eqMGWkqBdOSG/nwXe7RuLf+sn2EGlmyaLZkVc56UJsRUxwtWgcn2Cvdo7qAeo0tLaRoo gAEZImcZEYqUx++j4l7w6xILv6m0tIzYX1nzI=

Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; b=Pkz3ocfrshlVTdc1ngiEFZKXQIn/ZS777ArGYgCYWOhR5+nU9A6rfotElFmUTKbTkS 4y20XUu3fOoCeio1OLZtBML85EAOEEgAe5Ywo18vWyKCmCQKBhBoeqLIEZn7mbdeoxK5 MkGZOA+A6Jm7ausUEu3fzVVA/nfWVJEm87NDA=

Hi Chris,

That did the trick after I realized that that using the "USE_HEADERMAP NO" meant that no headers are found unless the paths are explicitly specified in the Header Search Paths of the target.

Thanks for your help,

Mike

On Sep 24, 2009, at 16:36, Chris Espinosa wrote:

On Sep 24, 2009, at 4:04 PM, Mike Collier wrote:

I have a project that has 3 targets with the only difference
between the targets being the HEADER INCLUDE PATHS and a define that
designates which target it is. I want to be able to compile my source
3 times, each time using the different include paths. This works
fine if I don't have any of the include files in my project. However,
I would like to have the header files in my project so I can view them
and use find to search in them. If I put the include files in my project
then the compile fails because the wrong include files are being used
in the targets.

My question is can I have include files in my project without them being used as the includes during a compile?

This usually works fine. The problem comes if all three header files have the same name.

Xcode uses a shortcut called the "header map" to help the compiler find header files. It gets confused when there are multiple header files with the same name.

Add the Custom Build Setting USE_HEADERMAP and set its value to NO for all targets, and things should work fine.

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

References:
	>Using target specific include paths (From: Mike Collier <email@hidden>)
	>Re: Using target specific include paths (From: Chris Espinosa <email@hidden>)