bitcoin-core/libbitcoinkernel.pc.in

prefix=@CMAKE_INSTALL_PREFIX@
exec_prefix=${prefix}
libdir=${prefix}/@CMAKE_INSTALL_LIBDIR@
includedir=${prefix}/@CMAKE_INSTALL_INCLUDEDIR@

Name: @CLIENT_NAME@ kernel library
Description: Experimental library for the @CLIENT_NAME@ validation engine.
Version: @CLIENT_VERSION_STRING@
Libs: -L${libdir} -lbitcoinkernel
Libs.private: -L${libdir} @LIBS_PRIVATE@
Cflags: -I${includedir}
build: Add a pkg-config file for libbitcoinkernel 2024-09-04 22:02:34 +02:00			`prefix=@CMAKE_INSTALL_PREFIX@`
			`exec_prefix=${prefix}`
			`libdir=${prefix}/@CMAKE_INSTALL_LIBDIR@`
			`includedir=${prefix}/@CMAKE_INSTALL_INCLUDEDIR@`

build: Rename `PACKAGE_` variables to `CLIENT_` The use of `PACKAGE_NAME` for the project's variable name is problematic, as this name is commonly used in CMake's interface variables. If third-party CMake code handles with scopes improperly, our `PACKAGE_NAME` variable could end up with an unexpected value. This change avoids such conflicts by renaming all `PACKAGE_` variables to `CLIENT_`. 2024-10-24 16:39:39 +01:00			`Name: @CLIENT_NAME@ kernel library`
build: use CLIENT_NAME in libbitcoinkernel.pc.in 2025-02-07 16:11:48 +00:00			`Description: Experimental library for the @CLIENT_NAME@ validation engine.`
build: Rename `PACKAGE_` variables to `CLIENT_` The use of `PACKAGE_NAME` for the project's variable name is problematic, as this name is commonly used in CMake's interface variables. If third-party CMake code handles with scopes improperly, our `PACKAGE_NAME` variable could end up with an unexpected value. This change avoids such conflicts by renaming all `PACKAGE_` variables to `CLIENT_`. 2024-10-24 16:39:39 +01:00			`Version: @CLIENT_VERSION_STRING@`
build: Add a pkg-config file for libbitcoinkernel 2024-09-04 22:02:34 +02:00			`Libs: -L${libdir} -lbitcoinkernel`
			`Libs.private: -L${libdir} @LIBS_PRIVATE@`
			`Cflags: -I${includedir}`