| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
Added by 17ab095 ("add libdir/exec_prefix to xcb-xproto.pc") with the
rationale of using it to find the python path, but later commits bd7a481
("pkg-config: Add sysroot prefix") and be9c255 ("Adjust to automake
1.16.4 changes") make this directly accessible.
By removing libdir from the pkgconfig file, the file becomes identical
for different ABIs.
Signed-off-by: Matt Turner <mattst88@gmail.com>
|
| |
|
| |
The pythondir variable is now defined relative to ${PYTHON_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>
|
| |
|
|
|
|
|
|
|
| |
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>
|
| | |
|
| | |
|
| |
|
|
|
| |
tarname to "xcb-proto", which matches the Debian package and looks better than
"xcbproto".
|
| |
|
