To me, that sounds very proper, and it is the way the CocoaPods is structuring things — if that is any reference for you
Alex > Am 16.05.2016 um 16:13 schrieb Alex Zavatone <z...@mac.com>: > > With all the talk we've been having about frameworks under iOS recently and a > few of us actually getting them going, what might benefit the group is > discussing how to properly structure our projects so that they are stored > correctly in git. > > Questions such as, should we use workspaces at all? If so, does the > workspace belong in its own git repo? Should each sub project have its own > repo? Should we use cocoapods at all? If so, why? > > Right now, I have one xcode project that creates a target framework and > target app to "host" the framework. > > Inside this project , I have dragged in another that makes the static lib > that the framework links to. > > Would it make better sense to use a workspace at the top level, have that in > a git repo, then each of the sub projects in their own repo? Structurally, > this seems to actually be proper. > > Thoughts? > > Thanks, > Alex Zavatone > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Xcode-users mailing list (Xcode-users@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/xcode-users/below%40mac.com > > This email sent to be...@mac.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
