Thanks for your response Jens. That's good info to know. I don't mind being a guinea pig on this, so I'll keep persevering. I'm not super adept at building my own dynamic libraries or frameworks. I just do a lot of trial and error. I do use a lot of third party frameworks and libraries though.
I did notice (and this is probably my main problem), that libsqlite3.dylib is being loaded up near the top of the log: *dyld: loaded: /usr/lib/libsqlite3.dylib* I'm just trying to track down why it's loading. I use a bunch of third party frameworks and I suspect one of them is loading it in. I've removed any reference to sqlite3 that I could find, but so far nothing has prevented it from loading. Even though it is loading, is there a way to have SQLCipher take priority? Thanks, Brendan On Monday, October 5, 2015 at 1:00:53 PM UTC-6, Jens Alfke wrote: > > > On Oct 5, 2015, at 11:31 AM, Brendan Duddridge <bren...@gmail.com > <javascript:>> wrote: > > So I have no idea how to properly integrate SQLCipher with Couchbase Lite > such that I don't have to have my libsqlcipher.dylib in a fixed location on > my drive. I've tried all the suggestions in the SOF post, but have yet to > find a proper solution. > > > Sorry about this. :( You’re sort of being the guinea pig for using > SQLCipher with CBL on Mac OS — or maybe someone else has used it, but they > were already expert at setting up embedded binaries so they didn’t have any > questions. > > The good news is that when we release CBL 1.2 we will include SQLCipher > binaries for all supported platforms, and build instructions. (Yes, we’re > working on encryption support for Android/Java and Xamarin/.NET too.) > > I did eventually get libsqlcipher to load from a relative location (I > think), but then it doesn't actually work. That is, the call to set the > encryption key on the database returns NO. So I'm still at a loss of how to > proceed. > > > The dyld log message you quoted looks correct. Make sure there is no other > log showing the system sqlite3.dylib being loaded. > You can also look at the line CBL logs at startup that includes the SQLite > version info, to check whether it matches what you built. > > Did you modify the CBL Mac target to link libsqlcipher.dylib instead of > libsqlite.dylib? > > Or should I not bother with SQLCipher since I don't know when or if > Couchbase will stop supporting SQLite and go with ForestDB support only. > > > We’ll be supporting it for a while yet. At least through 1.3, maybe > farther. (Actually, depending on how you interpret semantic versioning, we > might have to bump our version to 2.0 if we remove support for it.) > > —Jens > > PS: Out of curiosity, how big is your libsqlcipher.dylib? > -- 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 mobile-couchbase+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/a173bd0a-5e63-4ff2-b1f0-45e9180f42b6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
