Another approach would be to not use target dependencies at all, and instead use the scheme. If you click on "Edit scheme …" and then go to the "Build" item you can click on "+" to add your static libraries. You have to drag them above your app after adding. If your libraries have internal build dependencies on each other you also need to make sure that the order is correct and then uncheck the "Parallelize Build" checkbox.
Lasse
On Aug 28, 2013, at 7:38 AM, Jim Geist <
email@hidden> wrote:
I have a system that has several targets and some shared code. It is organized as a main application which was created with the initial workspace, several projects of static libraries which contain shared code between the main app and a utility app, and a project for the utility app. (There will eventually be more tool projects sharing the same libraries.)
For the main application, I was able to add the static library projects as target dependencies. However, when I click to add target dependencies to the utility app, none of the other projects or targets show up as addable.
I have a theory that this might be because the utility app is a child of the workspace/main app, and is therefore a sibling of the static libraries.
Does anyone have a suggestion as to how to structure the workspace so that this will work?
Thanks!!
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