Find a file
Christian Linhart 89b022fdac xinput: typedef for event_type_base
member event_type_base in struct InputClassInfo is a CARD8.
This patch replaces the type with the new typedef EventTypeBase
which is defined as a CARD8.

This does not alter the ABI or API for that struct because
typedefs do not appear in the ABI.
And C handles typedefs as aliases.
So there'll be no API issues as well.

The libxcb generator adds additional functions that implement
an iterator over this type.
This is harmless because adding code is ABI/API compatible.

The purpose of this change is to add more semantic info to this
member variable of this struct.

This helps with xcb-based generators or automatic code-checkers
and things like that.

Signed-off-by: Christian Linhart <chris@demorecorder.com>
2017-03-11 10:49:04 +01:00
doc optionally enforce serialization of pads 2016-01-27 06:39:14 +01:00
src xinput: typedef for event_type_base 2017-03-11 10:49:04 +01:00
xcbgen move symboltable lookup of sumof expr to the parser 2017-03-11 10:48:30 +01:00
.gitignore Add py-compile to .gitignore 2009-09-22 16:08:11 -04:00
autogen.sh autogen.sh: Implement GNOME Build API 2013-01-16 13:20:49 -05:00
configure.ac Release xcb-proto 1.12 2016-05-18 18:34:11 +02:00
COPYING Fix the year in the other COPYING. 2006-04-27 17:58:37 -07:00
HACKING Add note on pretty patches and src/.gitattributes 2013-11-14 20:23:24 +09:00
INSTALL Remove xcl and CVSROOT. 2006-02-18 16:49:41 -08:00
Makefile.am Add autogen.sh to EXTRA_DIST. 2012-02-10 17:44:33 +09:00
NEWS Release xcb-proto 1.12 2016-05-18 18:34:11 +02:00
README Add Python parser language-independent parts. 2008-04-19 04:30:21 -04:00
TODO Add test program for XFree86-DRI extension to xcb-demo. Mark XFree86-DRI extension as tested and working. 2006-04-27 14:14:54 -07:00
xcb-proto.pc.in add libdir/exec_prefix to xcb-xproto.pc 2011-11-10 15:36:54 +01:00

About xcb-proto
===============

xcb-proto provides the XML-XCB protocol descriptions that libxcb uses to
generate the majority of its code and API. We provide them separately
from libxcb to allow reuse by other projects, such as additional
language bindings, protocol dissectors, or documentation generators.

This separation between the XCB transport layer and the
automatically-generated protocol layer also makes it far easier to write
new extensions. With the Xlib infrastructure, client-side support for
new extensions requires significant duplication of effort. With XCB and
the XML-XCB protocol descriptions, client-side support for a new
extension requires only an XML description of the extension, and not a
single line of code.

Python libraries: xcb-proto also contains language-independent Python
libraries that are used to parse an XML description and create objects
used by Python code generators in individual language bindings.  These
libraries are installed into $(prefix)/lib/pythonX.X/site-packages.  If
this location is not on your system's Python path, scripts that import
them will fail with import errors.  In this case you must add the
install location to your Python path by creating a file with a `.pth'
extension in a directory that _is_ on the Python path, and put the
path to the install location in that file.  For example, on my system
there is a file named 'local.pth' in /usr/lib/python2.5/site-packages,
which contains '/usr/local/lib/python2.5/site-packages'.  Note that 
this is only necessary on machines where XCB is being built. 

Please report any issues you find to the freedesktop.org bug tracker,
at:

	<https://bugs.freedesktop.org/enter_bug.cgi?product=XCB>

Discussion about XCB occurs on the XCB mailing list:

        <mailto:xcb at lists.freedesktop.org>
        <http://lists.freedesktop.org/mailman/listinfo/xcb>

You can obtain the latest development versions of XCB using GIT.
For anonymous checkouts, use:

        git clone git://anongit.freedesktop.org/git/xcb/proto

For developers, use:

        git clone git+ssh://git.freedesktop.org/git/xcb/proto