libxml2/libxml-2.0-uninstalled.pc.in

prefix=
exec_prefix=
libdir=${pcfiledir}
includedir=${pcfiledir}/include
modules=@WITH_MODULES@

Name: libXML
Version: @VERSION@
Description: libXML library version2.
Requires@XML_PC_PRIVATE@: @XML_PC_REQUIRES@
Libs: -L${libdir} @XML_LIBS@ @XML_PC_LIBS_PRIVATE@ @XML_PC_LIBS@ @LIBS@
Cflags: @XML_INCLUDEDIR@ @XML_CFLAGS@
New file for building against uninstalled libxml2 builds. Support the Tue Sep 30 12:31:00 AEST 2003 Malcolm Tredinnick <malcolm@commsecure.com.au> * libxml-2.0-uninstalled.pc.in: New file for building against uninstalled libxml2 builds. * configure.in, Makefile.am: Support the *-uninstalled.pc file. 2003-09-30 02:36:08 +00:00			`prefix=`
			`exec_prefix=`
			`libdir=${pcfiledir}`
			`includedir=${pcfiledir}/include`
Update libxml-2.0-uninstalled.pc.in 2022-04-03 02:20:59 +02:00			`modules=@WITH_MODULES@`
New file for building against uninstalled libxml2 builds. Support the Tue Sep 30 12:31:00 AEST 2003 Malcolm Tredinnick <malcolm@commsecure.com.au> * libxml-2.0-uninstalled.pc.in: New file for building against uninstalled libxml2 builds. * configure.in, Makefile.am: Support the *-uninstalled.pc file. 2003-09-30 02:36:08 +00:00
			`Name: libXML`
			`Version: @VERSION@`
			`Description: libXML library version2.`
build: Generate better pkg-config files for static-only builds pkg-config supports `Requires.private` and `Libs.private` fields for static linking. However, if you're building a dynamic binary, then pkg-config will use the non-private fields, even if just the static libxml2 is available. This will result in libxml2 being underlinked, causing the build to fail. The solution is to fold the private fields into the non-private fields when the shared libxml2 is not being built. This works for Autotools and CMake. Meson also knows how to handle this when it automatically generates pkg-config files. 2023-09-02 17:12:58 +01:00			`Requires@XML_PC_PRIVATE@: @XML_PC_REQUIRES@`
			`Libs: -L${libdir} @XML_LIBS@ @XML_PC_LIBS_PRIVATE@ @XML_PC_LIBS@ @LIBS@`
autoconf: Don't bake build time CFLAGS into pkg-config file Having slept on it, I've realised that baking the dependency CFLAGS into the pkg-config file is pointless when it is only used to link against them. It may even cause problems. 2023-09-04 09:25:44 +01:00			`Cflags: @XML_INCLUDEDIR@ @XML_CFLAGS@`