xorg-xcbproto/xcb-proto.pc.in

prefix=@prefix@
exec_prefix=@exec_prefix@
datarootdir=@datarootdir@
datadir=@datadir@
xcbincludedir=${pc_sysrootdir}@xcbincludedir@
PYTHON_PREFIX=@PYTHON_PREFIX@
pythondir=${pc_sysrootdir}@pythondir@

Name: XCB Proto
Description: X protocol descriptions for XCB
Version: @PACKAGE_VERSION@
Remove xcl and CVSROOT. 2006-02-18 16:49:41 -08:00			`prefix=@prefix@`
add libdir/exec_prefix to xcb-xproto.pc If we want to base other paths off of exec_prefix or libdir (like the python path), we can't because the xcb-proto.pc.in file omits those variables. Add them so people can leverage them in their own builds. Signed-off-by: Mike Frysinger <vapier@gentoo.org> Signed-off-by: Julien Danjou <julien@danjou.info> 2011-11-08 16:57:44 -05:00			`exec_prefix=@exec_prefix@`
Move XML protocol descriptions to $datadir/xcb (generally $prefix/share/xcb). 2006-09-25 03:27:27 -07:00			`datarootdir=@datarootdir@`
			`datadir=@datadir@`
pkg-config: Add sysroot prefix xcb-proto's pkg-config file exports static file paths for where to find its Python files and the XML definitions. When used to discover cflags, library paths, etc, pkg-config will prepend ${PKG_CONFIG_SYSROOT_DIR}, if any, to those paths. This makes the use of a sysroot prefix transparent to users. However, since it doesn't know about paths in custom variables, it cannot automatically prefix this. Adding ${pc_sysrootdir} to these absolute paths makes the behaviour match, and XCB builds work out of the box in a sysroot. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> 2017-09-27 18:16:22 +01:00			`xcbincludedir=${pc_sysrootdir}@xcbincludedir@`
Adjust to automake 1.16.4 changes The pythondir variable is now defined relative to ${PYTHON_PREFIX}. 2021-09-09 13:17:20 +00:00			`PYTHON_PREFIX=@PYTHON_PREFIX@`
pkg-config: Add sysroot prefix xcb-proto's pkg-config file exports static file paths for where to find its Python files and the XML definitions. When used to discover cflags, library paths, etc, pkg-config will prepend ${PKG_CONFIG_SYSROOT_DIR}, if any, to those paths. This makes the use of a sysroot prefix transparent to users. However, since it doesn't know about paths in custom variables, it cannot automatically prefix this. Adding ${pc_sysrootdir} to these absolute paths makes the behaviour match, and XCB builds work out of the box in a sysroot. Signed-off-by: Daniel Stone <daniels@collabora.com> Reviewed-by: Eric Anholt <eric@anholt.net> 2017-09-27 18:16:22 +01:00			`pythondir=${pc_sysrootdir}@pythondir@`
Remove xcl and CVSROOT. 2006-02-18 16:49:41 -08:00
Change human-readable name from "XCBProto" to "XCB Proto"; this changes the tarname to "xcb-proto", which matches the Debian package and looks better than "xcbproto". 2006-04-15 19:39:39 -07:00			`Name: XCB Proto`
Remove xcl and CVSROOT. 2006-02-18 16:49:41 -08:00			`Description: X protocol descriptions for XCB`
			`Version: @PACKAGE_VERSION@`