Frameworks, static libraries and multiple targets for multiple SDKs
Frameworks, static libraries and multiple targets for multiple SDKs
- Subject: Frameworks, static libraries and multiple targets for multiple SDKs
- From: Eyal Redler <email@hidden>
- Date: Sat, 20 Feb 2010 19:24:48 +0200
Hi,
This question(s) is a bit all over the place but I'm afraid this is how my mind is when I try to figure out this out.
I have several projects, all of which share a lot of code. I'm using static libraries which are used as sub projects of the various projects in which I use the code.
In the past, each static library had only one target which was used in a Mac application but I now want to use the libraries for building an iPhone application so I've added an iPhone/iPad target to the library projects. With that in mind I have the following questions:
1. Should I re-add the system frameworks for the new target?
2. I'm not sure I understand why I need to add the frameworks in a static library, it seems that the library project can build just fine on its own even If I don't have any framework marked as the target member.
3. I noticed that there is an SDK for the Simulator and an SDK for the device, should I have separate targets for the simulator and the device or does the selection of "Active SDK" in the main project (which includes the library sub-projects) propagate to the library sub projects.
TIA
Eyal Redler
------------------------------------------------------------------------------------------------
"If Uri Geller bends spoons with divine powers, then he's doing it the hard way."
--James Randi
www.eyalredler.com
_______________________________________________
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