libxml2/libxml-2.0.pc.in

prefix=@prefix@
exec_prefix=@exec_prefix@
libdir=@libdir@
includedir=@includedir@
modules=@WITH_MODULES@

Name: libXML
Version: @VERSION@
Description: libXML library version2.
Requires: @XML_PC_REQUIRES@
Libs: -L${libdir} @XML_LIBS@
Libs.private: @XML_PC_LIBS@ @LIBS@
Cflags: @XML_INCLUDEDIR@ @XML_CFLAGS@ @XML_PC_CFLAGS@
Revert directory structure changes 2001-02-23 17:55:21 +00:00			`prefix=@prefix@`
			`exec_prefix=@exec_prefix@`
			`libdir=@libdir@`
			`includedir=@includedir@`
applied DSO support patch 2 from Joel Reed Daniel * Makefile.am config.h.in configure.in error.c libxml-2.0.pc.in testModule.c testdso.c xml2-config.in xmllint.c xmlmodule.c include/libxml/Makefile.am include/libxml/xmlerror.h include/libxml/xmlmodule.h include/libxml/xmlversion.h.in include/libxml/xmlwin32version.h.in: applied DSO support patch 2 from Joel Reed Daniel 2005-01-04 15:10:22 +00:00			`modules=@WITH_MODULES@`
Revert directory structure changes 2001-02-23 17:55:21 +00:00
			`Name: libXML`
			`Version: @VERSION@`
moved includes to includedir/libxml2/libxml, updated the configuration * config.h.in configure.in libxml.spec.in include/libxml/Makefile.am libxml-2.0.pc.in: moved includes to includedir/libxml2/libxml, updated the configuration scripts systems accordingly 2001-09-12 20:19:58 +00:00			`Description: libXML library version2.`
build: Generate better pkg-config file for SYSROOT builds The -I and -L flags you use to build should not necessarily be the same ones you bake into installed files. If you are building with dependencies located under a SYSROOT then the installed files should have no knowledge of that SYSROOT. For example, if the build requires `-L/path/to/sysroot/usr/lib/foo` then only `-L/usr/lib/foo` should be baked into the installed files. pkg-config is SYSROOT-aware, so this issue can be sidestepped by using the `Requires` field rather than the `Libs` and `Cflags` fields. This is easily resolved if you rely solely on pkg-config, but this project falls back to standard Autoconf checks, so a little more effort is required. Unfortunately, this issue cannot feasibly be resolved for CMake. `find_package` is used rather than `pkg_check_modules`, so we cannot tell whether a pkg-config file for each dependency is present or not, even if `find_package` uses pkg-config behind the scenes. The CMake build does not record any dependency -I or -L flags into the pkg-config file anyway. This is a problem in itself, although these dependencies are most likely installed to standard locations. Meson is very much better at handling this, as it generates the pkg-config file automatically using the correct logic. 2023-09-02 16:18:30 +01:00			`Requires: @XML_PC_REQUIRES@`
build: Make use of variables in libxml's pkg-config file Instead of hardcoding make use of available variables and optimize usage 2022-04-02 21:06:47 +02:00			`Libs: -L${libdir} @XML_LIBS@`
build: Generate better pkg-config file for SYSROOT builds The -I and -L flags you use to build should not necessarily be the same ones you bake into installed files. If you are building with dependencies located under a SYSROOT then the installed files should have no knowledge of that SYSROOT. For example, if the build requires `-L/path/to/sysroot/usr/lib/foo` then only `-L/usr/lib/foo` should be baked into the installed files. pkg-config is SYSROOT-aware, so this issue can be sidestepped by using the `Requires` field rather than the `Libs` and `Cflags` fields. This is easily resolved if you rely solely on pkg-config, but this project falls back to standard Autoconf checks, so a little more effort is required. Unfortunately, this issue cannot feasibly be resolved for CMake. `find_package` is used rather than `pkg_check_modules`, so we cannot tell whether a pkg-config file for each dependency is present or not, even if `find_package` uses pkg-config behind the scenes. The CMake build does not record any dependency -I or -L flags into the pkg-config file anyway. This is a problem in itself, although these dependencies are most likely installed to standard locations. Meson is very much better at handling this, as it generates the pkg-config file automatically using the correct logic. 2023-09-02 16:18:30 +01:00			`Libs.private: @XML_PC_LIBS@ @LIBS@`
			`Cflags: @XML_INCLUDEDIR@ @XML_CFLAGS@ @XML_PC_CFLAGS@`