Ok, through some trials in the WorkspaceExperiment [1] I've got the magic
ordering:
To embed a framework that's the output of a sibling project within the same
Xcode workspace:
1. Build HelloFramework for iOS, _not_ for simulator
2. Go to Project Navigator > HelloApp > Target > Build Phases
3.
Thanks Quincey,
The easy thing to check is to look at the build phases for the app, and
> make sure that the framework is listed in the Target Dependencies phase.
When I tap on the plus sign next to the Target Dependencies build phase,
the framework target is not listed as an option. That is,
On Aug 15, 2016, at 19:28 , Lou Zell wrote:
>
> So it looks like when I embed a binary through the general tab, it is only
> of the currently built binary located in derived data! I have tried
> rebuilding the framework for a device, but then I get the same error on the
>
Hello,
tl;dr; what is the proper way to have a framework project as a dependency
in another project in the same workspace?
I have a framework A that gets embedded in an iOS app B. My Xcode
workspace has different projects for A and B. The framework A will be
distributed, but it is also used as