* [sqlite3] Update to 3.42.0
* version
* Add cmake wrapper
* Test cmake wrapper
* version
* Add libsqlite3 to library names
* version
* WIP
* version
* restore original
* Remove cmake wrapper
* version
* Remove wrapper
* Remove all unused features
* version
* Remove unused features
* version
* only remove 1 variable
* version
* .
* version
* make json1 default feature
* version
* [sqlite3] Control features with a configuration header rather than CMake or pkgconfig.
Resolves https://github.com/microsoft/vcpkg/pull/29335
Alternate of https://github.com/microsoft/vcpkg/pull/29258
@Neumann-A points out that controlling features through CMake configs and pkgconfig causes MSBuild customers to be left out in the cold. Moreover, attempting to add parenthesis to the SQLITE_API marco breaks autotools. This change makes such parenthesis unnecessary and ensures the configuration bits are used with automatic linking.
* Ensure feature controls affect the .c too, use less MAYBE_UNUSED.
* Correctly note that zlib has no effect without tools.
* Always add DL_LIBS even when static linking.
* [sqlitecpp] Unconditionally enable column metadata because that is done in the sqlite3 port.
* Add missing -l prefix on CMAKE_DL_LIBS
* [sqlite3] Remove the restriction of using find_dependency(Threads) only under static linking
* x-add-version
Co-authored-by: Cheney-Wang <v-xincwa@microsoft.com>
* [sqlite3] Add more features
* version
* Add dependency zlib for feature zlib
* version
* Remove -DSQLITE_API=extern
* version
* Add pre-defines to pkgconfig
* Add new option CFLAGS to get all clfags
* Get pkgconfig cflags, add sqlite3 feature dependency
* version
* doc
* [libdjinterop] update to 0.16.0
* [sqlite3] add pkgconfig file
Linux distributions typically use the SQLite autoconf package,
but this port uses the SQLite amalgamation package with a custom
CMakeLists.txt so the port needs to take care of installing the
pkgconfig file.
