[package] <sqlcipher>/<4.5.0>: Should SQLCipher expose the same define options as SQLite3?

conan-io / conan-center-index

Recipes for the ConanCenter repository

https://conan.io/center

MIT License

945 stars 1.72k forks source link

[package] <sqlcipher>/<4.5.0>: Should SQLCipher expose the same define options as SQLite3? #8887

Open Einh06 opened 2 years ago

Einh06 commented 2 years ago

Since SQLCipher is an extension on top of SQLite3, shouldn't all the options available in sqlite3 be also available for the sqlcipher package?

SpaceIm commented 2 years ago

It depends whether sqlcipher has internal build logic based on how sqlite3 was built. If there is some logic, I don't think options should be duplicated, but instead sqlite3 options values should contribute to package id of sqlcipher.

Einh06 commented 2 years ago

From what I read on their documentation(packaging section), SQLCipher is a source extension of SQLite. From my understanding, that would mean that all available configuration, especially, define options like SQLITE_DEFAULT_JOURNAL_SIZE_LIMIT;SQLITE_ENABLE_MEMORY_MANAGEMENT;... should be supported. (When building a amalgamation from sqlcipher source, all the flags are avaiable).