summaryrefslogtreecommitdiffstats
path: root/configs/autoconf.in
Commit message (Collapse)AuthorAgeFilesLines
* Add --with-dri-searchpath argumentChow Loong Jin2009-10-301-1/+1
| | | | | | | * Add an extra argument to configure which allows for specifying different DRI driver search paths to libGL (FDO #24766) Signed-off-by: Dan Nicholson <[email protected]>
* Merge remote branch 'origin/master' into radeon-rewriteDave Airlie2009-06-071-0/+1
|\
| * Use separate $(MINSTALL) for installing librariesDan Nicholson2009-06-011-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | The special feature of bin/minstall to copy symlinks is only ever needed when installing libraries which may have .so symlinks. All the headers and directories can use a normal install program. These two modes are separated as $(INSTALL) and $(MINSTALL) to allow the user (or autoconf) to override installing normal files as they please. An autoconf check for the install program has been added and will be used in preference to minstall when available. Fixes bug 16053.
* | Merge remote branch 'main/master' into radeon-rewriteDave Airlie2009-03-201-2/+6
|\| | | | | | | | | | | | | | | | | Conflicts: src/mesa/drivers/dri/r300/r300_cmdbuf.c src/mesa/drivers/dri/r300/r300_state.c src/mesa/drivers/dri/r300/r300_swtcl.c src/mesa/drivers/dri/r300/radeon_ioctl.c src/mesa/drivers/dri/radeon/radeon_screen.c
| * st/xorg: Install to XORG_DRIVER_INSTALL_DIRJoel Bosveld2009-03-061-0/+3
| |
| * autoconf: Fixup EGL buildDan Nicholson2009-02-251-0/+1
| | | | | | | | This gets the needed libraries pulled in for libEGL for autoconf.
| * gallium: s/GALLIUM_DRIVER_DIRS/GALLIUM_DRIVERS_DIRS/Jakob Bornecrantz2009-02-201-2/+2
| |
* | radeon: add cflags to decide whether to link libdrm_radeon or not.Dave Airlie2009-02-151-0/+2
|/ | | | | You don't need libdrm_radeon for the legacy driver to build, only for the experimental mm/cs paths.
* autoconf: Adjust to new asm SOURCES variablesDan Nicholson2009-02-111-2/+2
| | | | | | | | Commit 90b2beb661f630966788a6e909dc759c99e38973 changed the assembly variables. Without this change, the glapi assembly wasn't being built when it was supposed to, resulting in missing symbols in libGL. Signed-off-by: Dan Nicholson <[email protected]>
* gallium: Update autoconf to latest gallium buildJakob Bornecrantz2009-02-111-2/+5
|
* mesa: merge gallium-0.2 into gallium-master-mergeBrian Paul2009-02-091-1/+7
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Merge commit 'origin/gallium-0.2' into gallium-master-merge Conflicts: Makefile docs/relnotes-7.4.html docs/relnotes.html src/mesa/drivers/dri/i965/brw_wm.h src/mesa/main/imports.c src/mesa/main/mtypes.h src/mesa/main/texcompress.c src/mesa/main/texenvprogram.c src/mesa/main/version.h src/mesa/vbo/vbo_exec_api.c src/mesa/vbo/vbo_save_draw.c
| * gallium autoconf/automakeJerome Glisse2009-02-011-1/+7
| |
* | mesa: autoconf fixes for OS XSiddhartha Chaudhuri2009-02-091-0/+7
|/ | | | See bug report 17566.
* Add OSMesa pkg-config fileDan Nicholson2008-12-141-1/+2
| | | | This makes the GLU .pc file a little simpler, too.
* Add more package metadata to the pkg-config filesDan Nicholson2008-12-141-0/+17
| | | | | | | | | | | | | The pkg-config files have been filled in more thoroughly to allow users to use mesa more effectively. By adding metadata to Requires.private, Libs.private and Cflags, we can ensure that all the libraries and headers will be found in all situations. However, the full substitutions are only done when using the configure script. This also fixes the glu pkg-config file to account for using GL or OSMesa. Fixes bug 18161.
* autoconf: Support Motif widgets in GLw with --enable-motifDan Nicholson2008-07-181-0/+4
| | | | | | | | | | | | Add an --enable-motif option, which will enable the Motif widgets in libGLw and link it with libXm. The Motif installation information will be gathered from the motif-config script (this comes with LessTif) or fallback to the standard autoconf checks. To allow the location of the Motif headers to be set from configure, the default setting of -I/usr/include/Motif1.2 has been moved into configs/default and then passed to the Makefile through the MOTIF_CFLAGS variable.
* Call minstall with $(SHELL) so the user controls the interpreterDan Nicholson2008-07-121-1/+0
| | | | | | Running minstall directly means that /bin/sh is always used as hte interpreter. If the user needs or wants to use a different shell fo minstall, they can use the SHELL make variable.
* autoconf: Subsitute SHELL for all platformsDan Nicholson2008-07-121-3/+1
| | | | | | | | | | | | | | Establish the shell that make will use from configure. This is exactly how autoconf/automake operate, with the environment variable CONFIG_SHELL respected to override the autoconf checks. In the usual case where the user just executes `./configure', autoconf will pick a shell from the current shell, sh, bash, ksh or sh5 that meets its base criteria. The special Solaris case of looking for a POSIX shell has been changed to just set the SHELL variable since autoconf substitutes this already. The EXTRA_CONFIG_LINES substitution is dropped as it should no longer be needed.
* Set library and header installation directories from configurationDan Nicholson2008-07-061-0/+3
| | | | | | | | | | | | | | Currently the installation directories for libraries and headers are resolved within the install commands. For instance, the libraries will be installed to $(INSTALL_DIR)/$(LIB_DIR). This limits the flexibility of the installation, such as when the libraries should be installed to a subdirectory like /usr/lib/tls. This adds the make variables $(INSTALL_LIB_DIR) and $(INSTALL_INC_DIR) to define the locations that the libraries and headers are installed. For the static configs, this resolves exactly as before to $(INSTALL_DIR)/include and $(INSTALL_DIR)/$(LIB_DIR). For autoconf, they are derived directly from the --libdir and --includedir settings.
* Solaris port of Mesa 7.1 with autoconf supportAlan Coopersmith2008-06-211-0/+3
| | | | Signed-off-by: Brian Paul <[email protected]>
* drop GLcoreGeorge Sapountzis2008-05-231-4/+0
|
* glcore: Set all external variables in configurationGeorge Sapountzis2008-05-051-0/+1
| | | | based on patch by Dan Nicholson <[email protected]>
* autoconf: Don't substitute MESA_MAJOR and friendsDan Nicholson2008-04-301-5/+0
| | | | | | 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/+3
|
* 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 gcc search patch to MKDEP_OPTIONS to eliminate warnings.Kristian Høgsberg2008-02-251-1/+1
| | | | | Also, use -include to avoid error message when make initially fails to include the non-existent depend file.
* autoconf: Allow static library buildsDan Nicholson2007-12-071-1/+1
| | | | | | | | | | | | | | 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: Configure the osmesa channel size for OSMesa16 and OSMesa32Dan Nicholson2007-12-071-1/+1
| | | | | | | | | | 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 shared DRI build on linux and freebsdDan Nicholson2007-12-071-0/+17
| | | | | | | | | 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/+87
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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-20 04:56:00 +0000