summaryrefslogtreecommitdiff
path: root/configs/autoconf.in
AgeCommit message (Collapse)Author
2008-05-05glcore: Set all external variables in configurationGeorge Sapountzis
based on patch by Dan Nicholson <dbn.lists@gmail.com>
2008-04-30autoconf: Don't substitute MESA_MAJOR and friendsDan Nicholson
Since the autoconf config inherits from default, we don't need to duplicate and substitute the MESA_* version numbers in configure.ac. The version number is only needed in configure for the help text.
2008-04-23glcore: build from mesaGeorge Sapountzis
2008-03-31DRI interface changes and DRI2 direct rendering support.Kristian Høgsberg
Add DRI2 direct rendering support to libGL and add DRI2 client side protocol code. Extend the GLX 1.3 create drawable functions in glx_pbuffer.c to call into the DRI driver when possible. Introduce __DRIconfig, opaque struct that represents a DRI driver configuration. Get's rid of the open coded __GLcontextModes in the DRI driver interface and the context modes create and destroy functions that the loader was requires to provide. glcore.h is no longer part of the DRI driver interface. The DRI config is GL binding agnostic, that is, not specific to GLX, EGL or other bindings. The core API is now also an extension, and the driver exports a list of extensions as the symbol __driDriverExtensions, which the loader must dlsym() for. The list of extension will always include the DRI core extension, which allows creating and manipulating DRI screens, drawables and contexts. The DRI legacy extension, when available, provides alternative entry points for creating the DRI objects that work with the XF86DRI infrastructure. Change DRI2 client code to not use drm drawables or contexts. We never used drm_drawable_t's and the only use for drm_context_t was as a unique identifier when taking the lock. We now just allocate a unique lock ID out of the DRILock sarea block. Once we get rid of the lock entirely, we can drop this hack. Change the interface between dri_util.c and the drivers, so that the drivers now export the DriverAPI struct as driDriverAPI instead of the InitScreen entry point. This lets us avoid dlsym()'ing for the DRI2 init screen function to see if DRI2 is supported by the driver.
2008-02-25autoconf: Add gcc search patch to MKDEP_OPTIONS to eliminate warnings.Kristian Høgsberg
Also, use -include to avoid error message when make initially fails to include the non-existent depend file.
2007-12-07autoconf: Allow static library buildsDan Nicholson
Allow the user to specify that they want static libraries through the --{enable,disable}-{static,shared} switches like libtool. The mesa build only allows for one at a time, so static will be chosen if someone has passed --enable-static or --disable-shared. This also allows the mklib options to be set at build time. This allows -static to be set for mklib, but any platform specific settings are allowed by setting MKLIB_OPTIONS for configure. Handling of the program libraries through the APP_LIB_DEPS variable is pretty ugly, but it seems to work.
2007-12-07autoconf: Configure the osmesa channel size for OSMesa16 and OSMesa32Dan Nicholson
Allow the user to specify channel bits of 16 or 32 to enable OSMesa16 or OSMesa32 instead of the default OSMesa. This option is controlled through the option --with-osmesa-bits=BITS and is only honored when the driver is osmesa. The osdemos are not enabled in the 16 or 32 bit case because the Makefile is currently hardcoded to link to -lOSMesa.
2007-12-07autoconf: Add support for shared DRI build on linux and freebsdDan Nicholson
Added autoconf bits to allow using DRI as the driver through the option --with-dri-driver=DRIVER. The options are x11 (default) and dri. Three DRI specific options for controlling the driver directory, direct rendering and TLS are also added. The DRI will probably not work for platforms besides linux and freebsd.
2007-12-07autoconf: Initial support for an autoconf configurationDan Nicholson
This adds the initial support for using autoconf configuration. Support is available for shared Xlib driver builds. Later this will be extended to dri and osmesa-only builds and possibly targetting non-X backends. Support for static library builds will also be added. The configure script fills in the autoconf config. This is then used by running `make autoconf' after ./configure. Testing has been done on Linux/GNU. The configure script tries to faithfully reproduce the current configs/linux* and configs/freebsd*. Other platforms can be handled later by adding similar statements and feature tests. Pkg-config is used to search for packages when possible. This makes the build much more flexible and robust to the user's configuration. This requires that the pkg-config autoconf macros pkg.m4 are included in aclocal.m4. This requires autoconf and aclocal from autoconf and automake, respectively.