Xcode 7.3.1. iOS.
I've noticed that sometimes it's pretty hard to add dependencies to build phases within projects in a workspace, depending on what you're working with and am looking for a recommendations on an approach to solve this.
Here's my project structure
Workspace Project A - all crappy non ARC code from 2011 in here and the Subprojects within A Target iOS app A Subproject 1 Target static lib 1 Subproject 2 Target static lib 2 Subproject 3 Target static lib 3 Subproject 4 Target static lib 4 Subproject 5 Target static lib 5
Project B Target B Lovely Framework Target iOS app A needs to have all the subprojects' static libs as build dependencies. I have no problem adding these. Both static lib of Subproject 2 and Project A need to have the Target B Lovely Framework as dependencies. This is where I have difficulty adding the dependencies.
The problem is that the projects for the static libraries don't have this section.
What I have works, builds, is magic and sucks less than what I started with (death to Other Linker Flags and Legacy Build Paths), but this is not good enough.
Before I succeed on wasting yet more time, should I stop right here and convert the static libs to frameworks? These static libs can't link to the new .tdb files anyway.
Looking for guidance on which path to modernize this is recommended.
TY. Alex Zavatone
|