- For now put xtrans in X11/Xtrans/X11, since libX11 is looking for it in <X11/...>

- For Xcomposite and Xdamage, don't link the build system out of the xc tree
- Link the public X11 headers into their own directory
- Add links to XKeysymDB and XErrorDB
- Add links to all the Xlib man pages
- Add links to the lcUniConv subdirectory
- Conditionally include config.h in Xlib source
parent 6769ccda
Once upon a midnight hour, long ago, in a galaxy, far, far, away, Xlib
was originally developed by Jim Gettys, of Digital Equipment
Corporation (now part of HP).
Warren Turkal did the autotooling in October, 2003.
Individual deveopers include (in no particular order): Sebastien
Marineau, Holger Veit, Bruno Haible, Keith Packard, Bob Scheifler,
Takashi Fujiwara, Kazunori Nishihara, Hideki Hiura, Hiroyuki Miyamoto,
Katsuhisi Yano, Shigeru Yamada, Stephen Gildea, Li Yuhong, Seiji Kuwari.
This work was supported by many organizations (in no particular
order), including the X Consortium, Digital Equipment Corporation,
Tektronix, The Open Group, OMRON, Wyse Technology, Fujitsu Limited,
Sun Microsystems, Fuji Xerox, Sony Corporation, Toshiba Corporation,
Massachusetts Institute of Technology, Silicon Graphics, the XFree86
Project, among others. Patches/fixes came from all over.
No doubt we've missed credits. Please let us know who should be credited.
This diff is collapsed.
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
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:
where SYSTEM can have one of these forms:
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
Print a summary of the options to `configure', and exit.
Print the version of Autoconf used to generate the `configure'
script, and exit.
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.
Alias for `--cache-file=config.cache'.
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).
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=include src nls man
pkgconfigdir = $(libdir)/pkgconfig
pkgconfig_DATA = x11.pc
Xlib is autotooled!
#define S(x, y) y##x
Please contact S(south.rr.com, wt@mid, and jim.gettys@hp.com) before doing
any commits on this module.
This is the libX11 from XFree86.
The goal of this project are (1) to get libX11 out of the huge
XF86 hunk of code, (2) to make it buildable with autotools, and
(3) keep the ability to easily merge bug fixes from libX11 in
XF86 into this code, (4) make it possible for people to work with
Xlib without having to deal with the entire XFree86 distribution,
so that bugs can get detected and fixed, (5) provide a place to
move the X library forward.
1 and 2 are related in that a new build system will need to be
developed to get libX11 building outside of the XF86 tree.
Autotools was chosen for a variety of reasons, not the least
of which was that it is very common in the open source community.
For 3, notice that the directory structure of the src subdirectory
is congruant to the directory structure of xc/lib/X11 in the
XFree86 tree. Absolutely, do not break this unless this becomes
the dominant libX11. This allows easier incorporation of patches
from the XFree86 libX11.
For 4, notice that the library can be built without having to build
everything else, so you can build and test enhancements without
replacing your entire X distribution.
For 5, see the xlibs@pdx.freedesktop.org mailing list. For example,
lots of "stuff" was pushed into Xlib that should have been stand-alone
libraries, since they are not of universal interest and touch the X
wire protocol. (Mea culpa; a mistake I made 15 years ago that didn't
matter much in the days before shared libraries has been amplified for
aeons- jg). And Xlib does not tolerate loss of its connection well,
and so on...
Thanks for checking this package out, Warren Turkal and Jim Gettys.
#! /bin/sh
srcdir=`dirname $0`
test -z "$srcdir" && srcdir=.
cd $srcdir
autoreconf -v --install || exit 1
cd $ORIGDIR || exit $?
$srcdir/configure --enable-maintainer-mode "$@"
# -*- Autoconf -*-
# Process this file with autoconf to produce a configure script.
# Checks for programs.
# Checks for pkg-config packages
PKG_CHECK_MODULES(X11, xextensions xtrans xau)
PKG_CHECK_MODULES(XDMCP, xdmcp, [xdmauth="yes"], [xdmauth="no"])
# Transport selection
AC_ARG_ENABLE(unix-transport,[ --disable-unix-transport ], [UNIXCONN=$enableval], [UNIXCONN=yes])
AC_ARG_ENABLE(tcp-transport, [ --disable-tcp-transport ], [TCPCONN=$enableval], [TCPCONN=yes])
AC_ARG_ENABLE(ipv6, [ --disable-ipv6 ], [IPV6CONN=$enableval], [IPV6CONN=yes])
if test "$UNIXCONN" = "yes"; then
AC_DEFINE(UNIXCONN,1,[Support UNIX socket connections])
if test "$TCPCONN" = "yes"; then
AC_DEFINE(TCPCONN,1,[Support TCP socket connections])
if test "$IPV6CONN" = "yes"; then
AC_DEFINE(IPv6,1,[Support IPv6 for TCP connections])
# Check for dlopen
AC_SEARCH_LIBS(dlopen,[dl svld])
if test x$ac_cv_search_dlopen = xno; then
if test x$ac_cv_search_shl_load != xno; then
[Use shl_load to load shared libraries])
AC_DEFINE(HAVE_DLOPEN,1,[Use dlopen to load shared libraries])
if test x$ac_cv_header_dlcfn_h -o x$ac_cv_header_dl_h; then
[Use the X cursor library to load cursors])
# Checks for header files.
dnl AC_CHECK_HEADERS([stdio.h stdlib.h math.h])
# Checks for typedefs, structures, and compiler characteristics.
# Checks for library functions.
# Checks for system services
# arch specific things
case $target_alias in
*os2*) os2="true" ;;
*) ;;
AM_CONDITIONAL(OS2, test x$os2 = xtrue)
[Disable Xlib support for Multithreading]),
case x$xthreads in
AC_DEFINE(XTHREADS,[],[Whether libX11 is compiled with thread support])
AC_DEFINE(XUSE_MTSAFE_API,[],[Whether libX11 needs to use MT safe API's])
if test "x$xdmauth" = "xyes"; then
echo checking dmcp
AC_CHECK_LIB(Xdmcp, XdmcpWrap, [xdmauth="yes"], [xdmauth="no"], [$XDMCP_LIBS])
case x$xdmauth in
echo setting flags
echo unsetting flags
AC_CHECK_FUNC(poll, [AC_DEFINE(USE_POLL, 1, [poll() function is available])], )
# Find keysymdef.h
for flag in $XPROTO_CFLAGS -I/usr/include; do
case "$KEYSYMDEF" in
case "$flag" in
dir=`echo "$flag" | sed 's/ *-I//'`
if test -f "$file"; then
case "$KEYSYMDEF" in
AC_MSG_ERROR([Cannot find keysymdef.h])