vcpkg/ports/sqlite3/sqlite3.pc.in

prefix=@CMAKE_INSTALL_PREFIX@
exec_prefix=${prefix}
libdir=${prefix}/lib
includedir=${prefix}/include

Name: SQLite
Description: SQL database engine
Version: @PKGCONFIG_VERSION@
Libs: -L${libdir} -lsqlite3
Libs.private: @PKGCONFIG_LIBS_PRIVATE@
Cflags: -I${includedir}
[libdjinterop] update to 0.16.0 (#20136) * [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. 2021-09-23 04:00:06 +08:00			`prefix=@CMAKE_INSTALL_PREFIX@`
			`exec_prefix=${prefix}`
			`libdir=${prefix}/lib`
			`includedir=${prefix}/include`

			`Name: SQLite`
			`Description: SQL database engine`
			`Version: @PKGCONFIG_VERSION@`
			`Libs: -L${libdir} -lsqlite3`
			`Libs.private: @PKGCONFIG_LIBS_PRIVATE@`
[sqlite3] Control features with a configuration header (#29376) * [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 2023-02-07 04:00:37 +08:00			`Cflags: -I${includedir}`