Re: Workspace and adding a dependency to a target. HOW THE HELL DO YOU DO THIS?
Re: Workspace and adding a dependency to a target. HOW THE HELL DO YOU DO THIS?
- Subject: Re: Workspace and adding a dependency to a target. HOW THE HELL DO YOU DO THIS?
- From: Alex Zavatone <email@hidden>
- Date: Thu, 05 Jan 2017 16:01:38 -0600
On Jan 5, 2017, at 3:52 PM, Jens Alfke wrote: On Jan 5, 2017, at 12:05 PM, Alex Zavatone < email@hidden> wrote:
How in hell do i add the framework from project 1 as a dependency to the target iOS app of project 2?
I can’t answer as I haven’t used this configuration; I don’t use workspaces at all, actually.
What I do is embed project 1 directly inside project 2. Then I can make targets in project 2 dependent upon targets in project 1.
It may be that Xcode won’t let you set up dependencies between sibling projects? After all, the two projects in your workspace don’t directly know about each other; only the workspace knows both of them. (But again, I don’t know much about workspaces so I could well be wrong.)
—Jens
That can't be the case. I have projects from 2012 with 1 workspace and all projects in that make libs or frameworks that another target app links to and has dependencies for.
The workspace docs also state that projects in a workspace share the same build folder.
What's amazing and infuriating is that I simply can't add the output of one project - as a dependency in another project's target app. But I sure can add that same framework to the Build Phases - Link Binaries wiith Libraries section and to the General - Embedded Binaries section by dragging the FW from the built Projects gorup of the other project in the left hand pane.
But adding it to the Dependency section or Build Phases? Impossible.
: / |
_______________________________________________
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