On 19 Aug 2016, at 6:17 am, Jens Alfke <[email protected]> wrote: > CocoaPods didn’t use to be flexible enough to build our project (which is > pretty complex.) It probably is now, but no one’s put the work into trying it.
Fair enough. I would be inclined to start looking in to this myself, if only I could get past a house-of-cards situation I've somehow introduced by adding a swift file to our shared framework and resume being able to get our project to build at all. (And my "modulemap hack" described yesterday has, of course, proven to be a non-starter because of duplicately-linked code. Sigh.) > In the near future, whenever we can drop support for iOS 7, we’ll probably > switch to only having a dynamic framework. The whole static-framework > approach was just to work around iOS apps’ inability to load dynamic > libraries. Cool; I'll be looking forward to that. Carthage looked like a possibility, but it seems to require user interaction simply to do a "carthage update", so that's a no-go. Maybe a git submodule is the next thing to explore in the mean time. thanks, -ben -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/74B86BC7-C396-4527-ADE0-D964D3634195%40kashoo.com. For more options, visit https://groups.google.com/d/optout.
