Awesome, not snarky at all. Happy to tackle it. I'll open an issue now and should hopefully have a PR in the next few days.
I'll check out that commit as well, sounds great. Thanks! On Friday, February 13, 2015 at 3:23:11 PM UTC-4, Jens Alfke wrote: > > > On Feb 13, 2015, at 10:42 AM, Kevin Lord <[email protected] <javascript:>> > wrote: > > It seems to me that one potential solution is to simply create an > additional dynamic framework build target with a deployment target of iOS > 8+ with 'Defines Module' set to YES, that those developers can use, while > other users can use the existing targets. Might this be an option? > > > Totally. I hope I can say ‘patches welcome!’ without sounding snarky — I’d > love to have this as an option, but I don’t know when we’d get around to it > ourselves. > > If you want to tackle this, take a look at the “CBL iOS Library” target, > which is what builds the static library for iOS. That will show you which > sources and build settings you need. The “CBL Mac” target is what builds > the Mac OS framework, so that might be useful for dylib-specific things; > for example, it specifies a .exp file that lists the symbols to export. > > (Oh, also, check whether we have an issue covering this in the Github > tracker. If we don’t, please add one.) > > —Jens > > PS: Since you’re using Swift, you might want to look at commit 041e3b0, > pushed to master yesterday. It adds the new “nullable” annotations to the > public @interfaces, so if you use Xcode 6.3 you’ll get cleaner bridged > Swift APIs with fewer “?” and “!”s. > -- 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/fcf7a5a3-c40b-47fe-9709-5966729ae546%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
