3 ms·
We had a huge issue with sqlite3-cipher using the same symbol prefixes as the regular sqlite3 project. We had to learn enough low level stuff to change the sym
by digitalsushi 12y ago
We had a huge issue with sqlite3-cipher using the same symbol prefixes as the regular sqlite3 project. We had to learn enough low level stuff to change the symbol names because we couldn't replace the OS libraries.
Sqlite3-cipher changed their symbol names to just sqlcipher, effectively making it an unrelated project. If this had been the case at the start, we would have saved a few weeks of learning enough about this little universe we don't normally go into.
Academically it was great for us to get our hands dirty, but that isn't the only thing that matters (unfortunately)
- FooBarWidget 12y agoCouldn't you just compile your sqlite3 with private symbol visibility and statically link to that?
- awda 12y agoYep. Build objects with -fvisibility=hidden, create a static library with `ar rcs libsqlite.a *.o`, and link your app with it and NOT dynamic libsqlite.
- kenrikm 12y agoI've run into a similar issue, I'm using FMDB with SQCipher and have finally got it to be reliable after way to much time digging into very low lvl SQLite stuff then I care to think about.
- azinman2 12y agoWhat was your solve?