The libxcb package provides an interface to the X Window System protocol, which replaces the current Xlib interface. Xlib can also use XCB as a transport layer, allowing software to make requests and receive responses with both.
This package is known to build and work properly using an LFS-7.0 platform.
Download (HTTP): http://xcb.freedesktop.org/dist/libxcb-1.7.tar.bz2
Download MD5 sum: 925699df361b99491165ebc12068056b
Download size: 316 KB
Estimated disk space required: 20.8 MB
Estimated build time: 0.3 SBU
libXau-1.0.6, libXdmcp-1.1.0, libpthread-stubs-0.3, libxslt-1.1.26, and xcb-proto-1.6
Doxygen-1.7.5 (to generate API documentation) and check-0.9.8 (to run tests)
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/libxcb
Install libxcb by running the following commands:
./configure $XORG_CONFIG --docdir='${datadir}'/doc/libxcb-1.7 &&
make
To test the results, issue: make check.
Now, as the root user:
make install
--docdir='${datadir}'/doc/libxcb-1.7:
This parameter ensures the libxcb
documentation is installed to a versioned directory.
--without-doxygen: This
switch can be used to disable the API documentation if Doxygen-1.7.5 is installed.
The libxcb developers have decided to be strict in asserting locking bugs in X11 applications. This is different than the behavior of libX11 when used on its own, and it will cause some applications to crash when they previously did not. When an application has these types of bugs, it will crash with the following assertion:
xcb_xlib_lock: Assertion `!c->xlib.lock' failed.
An environment variable, LIBXCB_ALLOW_SLOPPY_LOCK, can be set which will
allow the locking bugs to not crash the application. It is a
workaround that is known to be needed in a few cases. If it is
found that these bugs affect an application in use, add the
following to your system or personal profile:
export LIBXCB_ALLOW_SLOPPY_LOCK=1
$XORG_PREFIX/include/xcb and $XORG_PREFIX/share/doc/libxcb-1.7
Last updated on 2011-12-09 03:40:04 +0000