Comments on: How to create multiple targets for Xcode iPhone Projects

By: versatilemind.com » Blog Archive » Setting up multiple targets for iPhone projects

Tue, 26 Jan 2010 21:40:26 +0000

[...] Creating multiple targets for Xcode iPhone Projects [...]

By: Tal

Tal — Sun, 04 Oct 2009 11:31:10 +0000

Problem solved:
I couldn’t find what was the difference between the two target’s configurations. However, using ‘duplicate target’ on original target created a target copy which worked just fine with CoreData.

So.. it seems that ‘duplicate target’ may be a better starting point than ‘add new target’ as it solves non-standard configurations of the first target.

Cheers

By: Tal

Tal — Fri, 02 Oct 2009 14:05:07 +0000

Yeah it’s there. I’ve even removed them and added through ‘add->existing framework’ and it doesn’t work (only in the lite version). Odd.

By: samwize

samwize — Fri, 02 Oct 2009 10:49:36 +0000

@Tal
I am not sure the error is due to the steps here. But you might want to check that the frameworks are in the lite version target > Link Binary With Libraries

By: Tal

Tal — Fri, 02 Oct 2009 09:12:42 +0000

Hi,

Thanks for your post, it’s very useful. There might be something missing though (or maybe I missed something) – After doing the steps above my lite version does not compile.

I’ve got strange compilation errors concerning CoreData objects:

/iAppDelegate.h:14: error: expected specifier-qualifier-list before ‘NSManagedObjectModel’
iAppDelegate.h:15: error: expected specifier-qualifier-list before ‘NSManagedObjectContext’
….

and so on. I tried removing and adding the CoreData framework but that does not fix the problem..

By: Mark P.

Mark P. — Sat, 05 Sep 2009 21:35:02 +0000

Thanks, I got it. What I was doing was actually checking the “Copy…” checkbox, so the resource was copied physically into the project’s directory, hence the name conflict error. Now when adding a new resource, I save it in a separate directory, and when importing to the project I add it as reference, so I only uncheck the “Copy..” checkbox. This way if I have two resources with the same name for the different targets, I click on Get Info and select the correct target to be added (which is just another way to do the same.)

Thanks

By: samwize

samwize — Wed, 26 Aug 2009 06:24:24 +0000

@Mark

Yes your understanding is correct. The resources in the targets references to the actual copy.

Lets say you added both the default.png under Groups & Files. The first in /full/default.png and the second in /lite/default.png.

Under the new target’s Compiled Bundle Resources, you should delete the default.png, then drag the /lite/default.png to it. There should be no error.

By: Mark P.

Mark P. — Wed, 26 Aug 2009 04:31:37 +0000

Hi,

First of all thanks, your tutorial seems to be very straighforward, and so far the best I have seen from some others, it seems to have all I need for my project.

However I have a question. I create the new target and go through all the steps in step 1. Then when I try to add the target specific resources I have problems. for example as you say: “To make it work, you have to copy the correct Default.png to that target’s ‘Copy Bundle Resources’, and also to remove the incorrect Default.png.”, I am not able to follow your directions, e.g. if I try to copy the .png file first, I get an alert saying it cannot do that. Also, if I first delete the .png file, and then try to copy the new Default.png file. I get the same alert message.

From what I understand, when creating a new target and copying the original target’s resources, is not actually making a physical copy, but it is acting like a “view” in my perception (e.g. the two groups of resources in the two targets are actually only “references” pointing to the same single resources on disk. So when I first delete the resource on the new target, I am actually only deleting the reference, so when I try to copy another Default.png, I won’t work because of the original .png file still on disk.

Does this make sense?? Sorry on the long post!

Am I doing something wrong, or missing something?? Your support is greatly appreciated, I guess this is the only thing preventing me from getting me where I want to get to.

Thank you in advance!

By: Just2us » Blog Archive » Tutorial: Creating multiple targets for … | IPhoneMate

Mon, 17 Aug 2009 20:11:20 +0000

[...] the original here: Just2us » Blog Archive » Tutorial: Creating multiple targets for … Share and [...]

By: Stu

Stu — Sun, 16 Aug 2009 12:58:05 +0000

To address the concern of accidentally not having LITE_VERSION set as a preprocessor macro (and thus releasing a full version accidentally), I put this little snippet of code into a header file (it only needs to be in one place in the codebase, just make sure it’s common to all configurations):
#ifndef LITE_VERSION
#ifndef FULL_VERSION
#error You probably forgot to specify if this is the Lite or Full version of the app
#endif
#endif

I then set FULL_VERSION explicitly in the paid version (See step 3 above). This means that any configuration that didn’t get a macro of either LITE_VERSION or FULL_VERSION won’t compile.