aboutsummaryrefslogtreecommitdiffstats
path: root/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
...
* autoconf: Don't substitute MESA_MAJOR and friendsDan Nicholson2008-04-301-12/+1
| | | | | | 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.
* glcore: build from mesaGeorge Sapountzis2008-04-231-0/+4
|
* autoconf: Default the build to DRI on OS+CPU combos where it's expected.Eric Anholt2008-04-181-2/+17
|
* autoconf: Add dfbsd support.Hasso Tepper2008-04-091-2/+2
|
* Pick up dri2proto from the standard proto header include path.Kristian Høgsberg2008-04-021-1/+1
|
* Use AC_CHECK_PROGS to find alternate make programsDan Nicholson2008-03-311-6/+2
| | | | | | | | The autoconf macro AC_PATH_PROGS handles the case of searching for multiple program names already, so we don't need to open code it. Also changed the search to AC_CHECK_PROGS so that it doesn't set the full path unless the user specified. Finally, report back the found value at the end for what the user should run.
* DRI interface changes and DRI2 direct rendering support.Kristian Høgsberg2008-03-311-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* autoconf: Add a workaround for second AC_PROG_PATH not overwriting results.Eric Anholt2008-03-221-3/+4
|
* autoconf: automatically detect if -ldl is required.Eric Anholt2008-03-211-2/+7
| | | | This logic was copied from the xserver.
* Fix autoconf build on FreeBSD: detect gmake, and put -D*_SOURCE under linux.Eric Anholt2008-03-211-4/+7
|
* autoconf: Enable xdemos by default when we build libGLDan Nicholson2008-03-101-6/+7
| | | | | Since the xdemos only link to libGL now, we can enable them for all but the osmesa driver target.
* autoconf: Print GCC include path directly and be more robust using itDan Nicholson2008-03-071-4/+5
| | | | | | | | Rather than constructing the GCC include path from `-print-search-dirs', we can get the path directly from `-print-file-name=include'. This is used in the Linux kernel build, for example. If no output is returned from the command, then we don't append a -I path the the makedepend options.
* autoconf: Add gcc search patch to MKDEP_OPTIONS to eliminate warnings.Kristian Høgsberg2008-02-251-0/+9
| | | | | Also, use -include to avoid error message when make initially fails to include the non-existent depend file.
* autoconf: Fix thinko when checking freebsd CPU typesDan Nicholson2008-02-211-1/+1
|
* autoconf: Set the default drivers after checking platform specificsDan Nicholson2008-02-211-6/+7
| | | | | | The platform-specific overrides to the DRI drivers were being ignored because the default was being set first. Instead, have the default be a fallback after the platform checks.
* Trivial SELinux awareness. Enable with --enable-selinux.Adam Jackson2008-02-151-3/+14
| | | | | Avoids AVC warnings when allocating executable memory by first checking if the current process has permission to do so.
* autoconf: Use -fno-strict-aliasing on GCCDan Nicholson2008-01-151-0/+6
| | | | | This change adds -fno-strict-aliasing when using gcc and g++, just like the existing configs.
* Allow osmesa to be enabled or disabledDan Nicholson2008-01-111-22/+18
| | | | | | | | | | | | | | The conditional in src/mesa/Makefile currently hardcodes the cases where libOSMesa can be built on libGL. Likewise, the xlib case always includes libOSMesa in the stand-alone target. This changes the conditional to a loop over the DRIVER_DIRS variable. This means that any driver configuration can enable or disable osmesa. The current "stand-alone" rule is changed so that DRIVER_DIRS=x11 and DRIVER_DIRS="x11 osmesa" are both respected. The configure option is changed to --enable-gl-osmesa as this change allows libOSMesa to be built upon any of the libGL-enabling drivers.
* autoconf: Helper options for adding GCC 32/64 bit flagsDan Nicholson2007-12-261-0/+32
| | | | | | | Two new configure options to add -m32 or -m64 to the CFLAGS and CXXFLAGS when GCC is in use. By default, the user supplied options are environment variables are respected, but these options are quick helps for the common case of x86/x86_64 using GCC.
* autoconf: Improve help text for demos and DRI driversDan Nicholson2007-12-121-2/+2
| | | | | | Changed the text for the default demos to be "auto" instead of "yes" since that didn't make much sense in this context. Added an example value for the --with-dri-drivers option as suggested by Brian.
* autoconf: Update bug address and fix some autoconf warningsDan Nicholson2007-12-121-2/+4
| | | | | Point bug reports to Bugzilla like bugs.html. Also, a warning from autoconf w.r.t. AC_OUTPUT was cleaned up.
* autoconf: Consistently use xlib for the driver nameDan Nicholson2007-12-121-23/+23
| | | | | Brian suggested that there should be more consistency using xlib vs. x11 in the configure script. Changed the options and variables to suit.
* autoconf: Optional assembly usage with --disable-asmDan Nicholson2007-12-121-14/+31
| | | | | | Allow the user to disable use of assembly code through the --disable-asm option. This is only relevant on the platforms where assembly is normally enabled such as Linux and FreeBSD.
* autoconf: Report the compiler options in the summaryDan Nicholson2007-12-121-0/+12
| | | | | | Report the compiler flags and macros that will be used in the build. This just provides a quick way to see what configure has silently been doing.
* autoconf: Optional debug build with --enable-debugDan Nicholson2007-12-121-0/+18
| | | | | | Allow the user to set the compiler debug flags and macros through the option --enable-debug. This addes -DDEBUG to the macros and -g to the CFLAGS and CXXFLAGS if gcc and g++ are in use.
* autoconf: More informative errors when pkg-config macros undefinedDan Nicholson2007-12-121-0/+6
| | | | | | | Added a check that PKG_PROG_PKG_CONFIG is defined before calling it so the user can see a proper error. Without it, the generated configure script will just pass on to the next statement and bomb with a strange shell syntax error.
* autoconf: Replace configs/current symlink from configureDan Nicholson2007-12-111-1/+7
| | | | | | Rather than having the user run `make autoconf' and have the Makefile setup the configs/current -> autoconf symlink, we can just do that in configure. This allows the user to just run `make' to build.
* autoconf: Clearer help text for the enable/disable optionsDan Nicholson2007-12-111-13/+13
| | | | | Make it clearer what the defaults for the AC_ARG_ENABLE options are and how to change them.
* autoconf: Since default DRI drivers to build with masterDan Nicholson2007-12-111-9/+16
| | | | | Sync the default DRI_DIRS with the configs in master. Added some of the comments from there, too.
* autoconf: glut doesn't need XtDan Nicholson2007-12-111-2/+2
| | | | | Don't link glut with libXt since it's not needed. (see commit ce98779571eee3f51d9f571fecf8deb83dd60f78)
* autoconf: Output summary information from configureDan Nicholson2007-12-071-0/+44
| | | | | Report some of the common settings back to the user after configure has completed.
* autoconf: Configurable DRI driversDan Nicholson2007-12-071-9/+43
| | | | | | | | | | | | | | The user can request specific DRI drivers to build rather than the default of "all that build on this platform". This allows the list of drivers to be easily slimmed down. This is controlled through the option --with-dri-drivers. For example: ./configure --with-driver=dri --with-dri-drivers="i965,nouveau" Unfortunately, using this setting means the DRI drivers aren't filtered by platform anymore and you might try to build something that doesn't work.
* autoconf: Allow static library buildsDan Nicholson2007-12-071-12/+121
| | | | | | | | | | | | | | 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.
* autoconf: Configurable demos directoriesDan Nicholson2007-12-071-3/+40
| | | | | | | | | | The user can request specific demos directories to build in. For example: ./configure --with-demos="demos,xdemos" The drawback is that we don't check for the necessary libararies in that case, only that the directory in progs/ exists.
* autoconf: Configure the osmesa channel size for OSMesa16 and OSMesa32Dan Nicholson2007-12-071-2/+29
| | | | | | | | | | 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.
* autoconf: Add support for osmesa-only buildsDan Nicholson2007-12-071-11/+65
| | | | | | | | Added autoconf support for using OSMesa as the driver instead linking it to libGL. This is enabled through --with-driver=osmesa. To differentiate these cases, another option --enable-x11-osmesa is used to enable or disable building OSMesa when the driver is x11.
* autoconf: Add support for shared DRI build on linux and freebsdDan Nicholson2007-12-071-16/+174
| | | | | | | | | 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.
* autoconf: Initial support for an autoconf configurationDan Nicholson2007-12-071-0/+309
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.