Re: Xcode-users Digest, Vol 6, Issue 231 Re: iPhone target-specific headers for Xcode
Re: Xcode-users Digest, Vol 6, Issue 231 Re: iPhone target-specific headers for Xcode
- Subject: Re: Xcode-users Digest, Vol 6, Issue 231 Re: iPhone target-specific headers for Xcode
- From: Bess Ho <email@hidden>
- Date: Wed, 6 May 2009 18:02:17 -0700
I haven't done it myself on this approach. I know other developers use this approach. Keep info.plist the same. But you define different executable using Target "get info" tab configuration specific for different app release. It is a different architecture than using #if #else #end.
On 6 May 2009, at 8:58 AM, Sam Krishna wrote:
> How do I create a target-specific header file that's included
> automatically when I switch build targets back and forth between
> Lite and Pro for an iPhone application project?
I assume the target-specific header files all have the same name, and
you want #import <header.h> to refer to a file in one place for one
target, and another place for another?
There may be ways to do this, by fooling with the header search paths
in the separate targets (maybe putting the specifics in directories
that are sisters to the directory containing the project file). I
haven't tried this, and I don't know how it interacts with the project
root directory (Project Info / General) and SCM.
Instead, why not have header.h wrap the two different files, with
#ifdefs choosing between them?
#if defined(TARGET_1)
#import <header-target-1.h>
#elif defined(TARGET_2)
#import <header-target-2.h>
#else
#error Must define a TARGET macro!
#end
_______________________________________________
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