Commit 47ceed78 authored by Josh Triplett's avatar Josh Triplett Committed by Josh Triplett

Remove xcl and CVSROOT.

parents
Makefile
Makefile.in
aclocal.m4
autom4te.cache
compile
config.guess
config.log
config.status
config.sub
configure
depcomp
install-sh
libtool
ltmain.sh
missing
mkinstalldirs
*.pc
Copyright (C) 2001-2004 Bart Massey, Jamey Sharp, and Josh Triplett.
All Rights Reserved.
Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the
Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute,
sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so,
subject to the following conditions:
The above copyright notice and this permission notice shall
be included in all copies or substantial portions of the
Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS
BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.
Except as contained in this notice, the names of the authors
or their institutions shall not be used in advertising or
otherwise to promote the sale, use or other dealings in this
Software without prior written authorization from the
authors.
This diff is collapsed.
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
Basic Installation
==================
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'. You only need
`configure.ac' if you want to change it or regenerate `configure' using
a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. Run `./configure --help'
for details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not support the `VPATH'
variable, you have to compile the package for one architecture at a
time in the source code directory. After you have installed the
package for one architecture, use `make distclean' before reconfiguring
for another architecture.
Installation Names
==================
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
==========================
There may be some features `configure' cannot figure out
automatically, but needs to determine by the type of machine the package
will run on. Usually, assuming the package is built to be run on the
_same_ architectures, `configure' can figure that out, but if it prints
a message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
CPU-COMPANY-SYSTEM
where SYSTEM can have one of these forms:
OS KERNEL-OS
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the `--target=TYPE' option to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Defining Variables
==================
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
will cause the specified gcc to be used as the C compiler (unless it is
overridden in the site shell script).
`configure' Invocation
======================
`configure' recognizes the following options to control how it
operates.
`--help'
`-h'
Print a summary of the options to `configure', and exit.
`--version'
`-V'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`--cache-file=FILE'
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.
`--config-cache'
`-C'
Alias for `--cache-file=config.cache'.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.
SUBDIRS=src tests
pkgconfigdir = $(libdir)/pkgconfig
pkgconfig_DATA = xcb.pc
EXTRA_DIST=xcb.pc.in
#! /bin/sh
autoreconf -v --install || exit 1
./configure "$@"
# -*- Autoconf -*-
# Process this file with autoconf to produce a configure script.
AC_PREREQ(2.57)
AC_INIT([libXCB],
0.9,
[xcb@lists.freedesktop.org])
AC_CONFIG_SRCDIR([xcb.pc.in])
AM_INIT_AUTOMAKE([foreign dist-bzip2])
dnl This ifdef has no useful effect prior to automake 1.9, but in 1.9
dnl it allows the user to not have check.m4 installed.
m4_ifdef([AM_PATH_CHECK],[
AM_PATH_CHECK(0.8.2, [HAVE_CHECK=true], [HAVE_CHECK=false])
])
AM_CONDITIONAL(HAVE_CHECK, test x$HAVE_CHECK = xtrue)
AC_CONFIG_HEADERS([src/config.h])
AC_PROG_LIBTOOL
AC_PROG_CC
AC_PATH_PROG(XSLTPROC, xsltproc, no)
if test "$XSLTPROC" = "no"; then
AC_MSG_ERROR([XCB requires xsltproc.])
fi
HTML_CHECK_RESULT=false
if test x"$HAVE_CHECK" = xtrue; then
if test x"$XSLTPROC" != xno; then
HTML_CHECK_RESULT=true
fi
fi
AC_SUBST(HTML_CHECK_RESULT)
# Checks for pkg-config packages
PKG_CHECK_MODULES(XCBPROTO, xcb-proto >= 0.9)
PKG_CHECK_MODULES(XPROTO, xproto)
PKG_CHECK_MODULES(XAU, xau)
# Find the xcb-proto protocol descriptions
AC_MSG_CHECKING(XCBPROTO_XCBINCLUDEDIR)
XCBPROTO_XCBINCLUDEDIR=`$PKG_CONFIG --variable=xcbincludedir xcb-proto`
AC_MSG_RESULT($XCBPROTO_XCBINCLUDEDIR)
AC_SUBST(XCBPROTO_XCBINCLUDEDIR)
AC_HEADER_STDC
AC_SEARCH_LIBS(gethostbyname, nsl)
AC_SEARCH_LIBS(connect, socket)
xcbincludedir='${includedir}/X11/XCB'
AC_SUBST(xcbincludedir)
AC_ARG_WITH(opt,
AC_HELP_STRING([--with-opt], [compile with reasonable optimizations])
AC_HELP_STRING([--with-opt=FLAGS], [compile with specified FLAGS])
AC_HELP_STRING([--with-opt=small], [compile for smallest code])
AC_HELP_STRING([--with-opt=debug], [compile for debugging (default)]),
[
case "$withval" in
yes)
optflags="-O3"
;;
small)
optflags="-Os -fomit-frame-pointer -DNDEBUG"
;;
no|debug)
optflags="-g"
;;
*)
optflags="$withval"
;;
esac
])
AC_CACHE_CHECK([what compiler optimizations to apply], [optflags], [optflags="-g"])
AC_DEFINE(_XOPEN_SOURCE, 500, [Conform to Single Unix Specification.])
CDEBUGFLAGS="$optflags -Wall -pedantic -Wpointer-arith \
-Wstrict-prototypes -Wmissing-declarations -Wnested-externs"
AC_SUBST(CDEBUGFLAGS)
AC_CONFIG_FILES([Makefile src/Makefile tests/Makefile])
AC_CONFIG_FILES([xcb.pc])
AC_OUTPUT
compat
copyright
fd.o-*
stamp-*
tmp
files
libxcb0 (0.9-1pre2v4) unstable; urgency=low
pre2v1:
* Split into libxcb0 and libxcb0-dev.
* Change control file for new packages.
* Add install and dirs files for new packages.
* Update Build-Depends for renaming of fd.o-xau, fd.o-xproto, and
fd.o-xcb-proto.
* Remove fd.o prefix from package name.
* Change Maintainer to xcb@lists.freedesktop.org, move myself to
Uploaders, and add Jamey Sharp to Uploaders. Update copyright.debian
accordingly.
* Add Bugs field pointing to xcb@lists.freedesktop.org.
* Update homepage URL in description and copyright.debian to
http://xcb.freedesktop.org, and put it in a Homepage: field in the
description.
pre2v2:
* Add libxcb0-dbg package.
pre2v3:
* New upstream snapshot.
pre2v4:
* New upstream snapshot.
-- Josh Triplett <josh@freedesktop.org> Tue, 17 May 2005 12:53:53 -0700
fd.o-xcb (0.9-1) unstable; urgency=low
* New version using XSLT; works with XML descriptions in xcb-proto 0.9.
* Updated Debian packaging.
-- Josh Triplett <josh@freedesktop.org> Fri, 29 Oct 2004 15:11:09 -0700
fd.o-xcb (0.8-1) unstable; urgency=low
* Initial Release.
-- Jamey Sharp <sharpone@debian.org> Thu, 18 Mar 2004 00:09:03 -0800
Source: libxcb0
Priority: optional
Maintainer: XCB Developers <xcb@lists.freedesktop.org>
Uploaders: Jamey Sharp <sharpone@debian.org>, Josh Triplett <josh@freedesktop.org>
Build-Depends: x-dev, libxau-dev, xcb-proto, cdbs, debhelper (>= 4.1.76), pkg-config, autoconf, automake1.9 | automaken, libtool, xsltproc, check, binutils (>= 2.12.90.0.9)
Build-Conflicts: automake1.4, automake1.5, automake1.6
Standards-Version: 3.6.1
Bugs: mailto:xcb@lists.freedesktop.org
Package: libxcb0
Section: libs
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: X C Binding
Xlib has been the standard C binding for the X Window System protocol for
many years now. It is an excellent piece of work, but there are applications
for which it is not ideal. XCB builds on nearly two decades of experience
with X specifically and software engineering in general in an effort to
replace the aging Xlib code base.
.
This package contains the library files needed to run software using
XCB.
.
Homepage: http://xcb.freedesktop.org
Package: libxcb0-dev
Section: libdevel
Architecture: any
Depends: libxcb0 (= ${Source-Version}), x-dev
Description: X C Binding, development files
Xlib has been the standard C binding for the X Window System protocol for
many years now. It is an excellent piece of work, but there are applications
for which it is not ideal. XCB builds on nearly two decades of experience
with X specifically and software engineering in general in an effort to
replace the aging Xlib code base.
.
This package contains the header and library files needed to build software
using XCB.
.
Homepage: http://xcb.freedesktop.org
Package: libxcb0-dbg
Section: libdevel
Architecture: any
Depends: libxcb0 (= ${Source-Version})
Description: X C Binding, debugging symbols
Xlib has been the standard C binding for the X Window System protocol for
many years now. It is an excellent piece of work, but there are applications
for which it is not ideal. XCB builds on nearly two decades of experience
with X specifically and software engineering in general in an effort to
replace the aging Xlib code base.
.
This package contains the debugging symbols associated with libxcb0. gdb will
automatically use these symbols when debugging libxcb0.
.
Homepage: http://xcb.freedesktop.org
This package was debianized by Jamey Sharp <sharpone@debian.org> on
Thu, 18 Mar 2004 00:48:42 -0800, and later updated by Josh Triplett
<josh@freedesktop.org>. The package is co-maintained by the XCB developers
via the XCB mailing list <xcb@lists.freedesktop.org>.
It was downloaded from http://xcb.freedesktop.org.
Upstream Authors: Jamey Sharp <sharpone@debian.org>
Josh Triplett <josh@freedesktop.org>
Copyright:
usr/lib
usr/include
usr/X11R6/include/X11/*
usr/lib/lib*.a
usr/lib/lib*.so
usr/lib/pkgconfig/*
usr/lib/*.la
usr/lib/lib*.so.*
#!/usr/bin/make -f
DEB_DH_INSTALL_SOURCEDIR=debian/tmp
include /usr/share/cdbs/1/rules/debhelper.mk
include /usr/share/cdbs/1/class/autotools.mk
DEB_CONFIGURE_EXTRA_FLAGS = --with-opt
DEB_CONFIGURE_INCLUDEDIR = "\$${prefix}/X11R6/include"
DEB_DH_STRIP_ARGS=--dbg-package=libxcb0
debian/stamp-autotools-files:
autoreconf -v --install
touch debian/stamp-autotools-files
debian/copyright: debian/copyright.debian COPYING
cat $+ > $@
clean::
-rm -f debian/copyright
common-install-prehook-arch common-install-prehook-indep:: debian/copyright
This source diff could not be displayed because it is too large. You can view the blob instead.
body
{
background-color: #dddddd;
color: #000000;
padding: 8px;
margin: 0px;
}
div.title
{
text-align: center;
font-weight: bold;
font-size: 28px;
}
div.emph
{
text-align: left;
font-weight: bold;
}
div.section li.title
{
font-weight: bold;
font-size: 22px;
}
div.section li.subtitle
{
font-weight: bold;
font-size: 18px;
}
div.section li.subsubtitle
{
font-weight: bold;
font-size: 16px;
}
div.comp
{
border: thin solid #000000;
background-color: #ffffe0;
padding: 14px;
}
div.comp div.title
{
font-weight: bold;
font-size: 16px;
text-align: center;
}
div.comp div.xlib
{
font-family: monospace;
position: absolute;
width: 49%;
margin-left: 0px;
margin-top: 10px;
}
div.comp div.xcb
{
font-family: monospace;
position: relative;
margin-left: 51%;
margin-top: 10px;
}
pre.code
{
border: thin solid #000000;
background-color: #efefef;
padding: 4px;
text-align: left;
font-size: 10;
}
pre.text
{
border: thin solid #000000;
background-color: #efefef;
padding: 4px;
text-align: left;
font-size: 10;
}
span.code
{
font-family: monospace;
font-size: 10;
}
.deps
.libs
Makefile
Makefile.in
config.h
config.h.in
stamp-h1
*.lo
*.loT
*.la
xproto.c
xproto.h
xcb_types.c
xcb_types.h
extensions
X11
check_all
lib_LTLIBRARIES = libXCB.la
EXTHEADERS = \
extensions/bigreq.h \
extensions/composite.h \
extensions/damage.h \
extensions/glx.h \
extensions/shm.h \
extensions/shape.h \
extensions/randr.h \
extensions/record.h \
extensions/render.h \
extensions/res.h \
extensions/dpms.h \
extensions/sync.h \
extensions/xc_misc.h \
extensions/xevie.h \
extensions/xf86dri.h \
extensions/xfixes.h \
extensions/xprint.h \
extensions/xv.h \
extensions/xvmc.h
EXTSOURCES = \
extensions/bigreq.c \
extensions/composite.c \
extensions/damage.c \
extensions/glx.c \
extensions/shm.c \
extensions/shape.c \
extensions/randr.c \
extensions/record.c \
extensions/render.c \
extensions/res.c \
extensions/dpms.c \
extensions/sync.c \
extensions/xc_misc.c \
extensions/xevie.c \
extensions/xf86dri.c \
extensions/xfixes.c \
extensions/xprint.c \
extensions/xv.c \
extensions/xvmc.c
EXTENSIONS = $(EXTSOURCES) $(EXTHEADERS)
COREHEADERS = xproto.h xcb_types.h
CORESOURCES = xproto.c xcb_types.c
COREPROTO = $(CORESOURCES) $(COREHEADERS)
xcbinclude_HEADERS = xcb.h xcbext.h xcbxlib.h $(COREHEADERS) $(EXTHEADERS)
CFLAGS =
AM_CFLAGS = -include config.h $(CDEBUGFLAGS) $(XCBPROTO_CFLAGS) $(XPROTO_CFLAGS) $(XAU_CFLAGS)
libXCB_la_LIBADD = $(XCBPROTO_LIBS) $(XPROTO_LIBS) $(XAU_LIBS)
libXCB_la_SOURCES = \
xcb_conn.c xcb_out.c xcb_in.c xcb_ext.c xcb_xid.c \
xcb_list.c xcb_util.c xcb_xlib.c xcb_auth.c xcb_des.c \
$(COREPROTO) $(EXTENSIONS)
xcb_des.c:
touch xcb_des.c
BUILT_SOURCES = $(COREPROTO) $(EXTENSIONS)
CLEANFILES = $(COREPROTO) $(EXTENSIONS)
clean-local:
rmdir extensions || true
vpath %.xml $(XCBPROTO_XCBINCLUDEDIR) $(XCBPROTO_XCBINCLUDEDIR)/extensions
%.h: %.xml c-client.xsl
@n=`dirname $*`; test -d $$n || (echo mkdir $$n; mkdir $$n)
$(XSLTPROC) --stringparam mode header \
--stringparam base-path $(XCBPROTO_XCBINCLUDEDIR)/ \
--stringparam extension-path \
$(XCBPROTO_XCBINCLUDEDIR)/extensions/ \
-o $@ $(srcdir)/c-client.xsl $<
%.c: %.xml c-client.xsl
@n=`dirname $*`; test -d $$n || (echo mkdir $$n; mkdir $$n)
$(XSLTPROC) --stringparam mode source \
--stringparam base-path $(XCBPROTO_XCBINCLUDEDIR)/ \
--stringparam extension-path \
$(XCBPROTO_XCBINCLUDEDIR)/extensions/ \
-o $@ $(srcdir)/c-client.xsl $<
This diff is collapsed.
/*
* Copyright (C) 2001-2004 Bart Massey, Jamey Sharp, and Josh Triplett.
* All Rights Reserved.
*
* Permission is hereby granted, free of charge, to any person obtaining a
* copy of this software and associated documentation files (the "Software"),
* to deal in the Software without restriction, including without limitation
* the rights to use, copy, modify, merge, publish, distribute, sublicense,
* and/or sell copies of the Software, and to permit persons to whom the
* Software is furnished to do so, subject to the following conditions:
*
* The above copyright notice and this permission notice shall be included in
* all copies or substantial portions of the Software.
*
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
* AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
* ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
* CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
*
* Except as contained in this notice, the names of the authors or their
* institutions shall not be used in advertising or otherwise to promote the
* sale, use or other dealings in this Software without prior written
* authorization from the authors.
*/
#ifndef __XCB_H
#define __XCB_H
#include <X11/Xmd.h>
#include <X11/X.h>
#include <sys/uio.h>