Compilation and Installation using Autoconf
-
-
- -
- +
- -
-
-
- GLU -
make realclean before rebuilding.
Some of the generic autoconf options are used with Mesa: - -
-
-
--prefix=PREFIX- This is the root directory where + +-
+
--prefix=PREFIX
+This is the root directory where files will be installed by
make install. The default is -/usr/local. -
---exec-prefix=EPREFIX- This is the root directory +/usr/local. + + +--exec-prefix=EPREFIXThis is the root directory where architecture-dependent files will be installed. In Mesa, this is only used to derive the directory for the libraries. The default is -
${prefix}. -
---libdir=LIBDIR- This option specifies the directory +${prefix}. + + +--libdir=LIBDIRThis option specifies the directory where the GL libraries will be installed. The default is
${exec_prefix}/lib. It also serves as the name of the library staging area in the source tree. For instance, if the option--libdir=/usr/local/lib64is used, the libraries will be created in alib64directory at the top of the Mesa source -tree. -
---enable-static, --disable-shared- By default, Mesa +tree. + + +--enable-static, --disable-sharedBy default, Mesa will build shared libraries. Either of these options will force static libraries to be built. It is not currently possible to build static and -shared libraries in a single pass. -
-CC, CFLAGS, CXX, CXXFLAGS- These environment variables +shared libraries in a single pass. + + +CC, CFLAGS, CXX, CXXFLAGSThese environment variables control the C and C++ compilers used during the build. By default,
gccandg++are used with the options -"-g -O2". -
-LDFLAGS- An environment variable specifying flags to +"-g -O2". + + +LDFLAGSAn environment variable specifying flags to pass when linking programs. These are normally empty, but can be used to direct the linker to use libraries in nonstandard directories. For -example,
LDFLAGS="-L/usr/X11R6/lib". -
-PKG_CONFIG_PATH- When available, the +example,LDFLAGS="-L/usr/X11R6/lib". + + +PKG_CONFIG_PATHWhen available, the
pkg-configutility is used to search for external libraries on the system. This environment variable is used to control the search path forpkg-config. For instance, settingPKG_CONFIG_PATH=/usr/X11R6/lib/pkgconfigwill search for package metadata in/usr/X11R6before the standard -directories. -
-
There are also a few general options for altering the Mesa build: -
-
-
--with-x- When the X11 development libraries are -needed, thepkg-configutility will -be used for locating them. If they cannot be found through -pkg-configa fallback routing usingimakewill -be used. In this case, the--with-x, ---x-includesand--x-librariesoptions can -control the use of X for Mesa. -
---enable-gl-osmesa- The OSMesa -library can be built on top of libGL for drivers that provide it. -This option controls whether to build libOSMesa. By default, this is -enabled for the Xlib driver and disabled otherwise. Note that this -option is different than using OSMesa as the driver. -
---enable-debug- This option will enable compiler -options and macros to aid in debugging the Mesa libraries. -
---disable-asm- There are assembly routines + +-
+
--enable-debug
+This option will enable compiler +options and macros to aid in debugging the Mesa libraries.
+
+
+--disable-asm
+There are assembly routines available for a few architectures. These will be used by default if one of these architectures is detected. This option ensures that -assembly will not be used. -
---enable-32-bit, --enable-64-bit- By default, the -build will compile code as directed by the environment variables +assembly will not be used. + + +--enable-32-bit--enable-64-bitBy default, the build will compile code as directed by the environment +variables
CC,CFLAGS, etc. If the compiler isgcc, these options offer a helper to add the compiler flags to force 32- or 64-bit code generation as used on the x86 and x86_64 -architectures. -
-
2. Driver Options
@@ -145,30 +153,30 @@ architectures. There are several different driver modes that Mesa can use. These are described in more detail in the basic installation instructions. The Mesa driver is controlled through the -configure option --with-driver. There are currently three supported -options in the configure script. +configure options--enable-xlib-glx, --enable-osmesa,
+and --enable-dri.
-Xlib
This is the default mode for building Mesa. +
Xlib
It uses Xlib as a software renderer to do all rendering. It corresponds
-to the option --with-driver=xlib. The libX11 and libXext
+to the option --enable-xlib-glx. The libX11 and libXext
libraries, as well as the X11 development headers, will be need to
support the Xlib driver.
-
DRI
This mode uses the DRI hardware drivers for +
DRI
This mode uses the DRI hardware drivers for
accelerated OpenGL rendering. Enable the DRI drivers with the option
---with-driver=dri. See the basic
+--enable-dri. See the basic
installation instructions for details on prerequisites for the DRI
drivers.
-
-
--with-dri-driverdir=DIR-This option specifies the +
--with-dri-driverdir=DIR+This option specifies the location the DRI drivers will be installed to and the location libGL will search for DRI drivers. The default is
${libdir}/dri. ---with-dri-drivers=DRIVER,DRIVER,...-This option +
--with-dri-drivers=DRIVER,DRIVER,...+This option allows a specific set of DRI drivers to be built. For example,
--with-dri-drivers="swrast,i965,radeon,nouveau". By default, the drivers will be chosen depending on the target platform. @@ -177,16 +185,16 @@ for available drivers. Beware that the swrast DRI driver is used by both libGL and the X.Org xserver GLX module to do software rendering, so you may run into problems if it is not available. ---disable-driglx-direct-Disable direct rendering in +
--disable-driglx-direct+Disable direct rendering in GLX. Normally, direct hardware rendering through the DRI drivers and indirect software rendering are enabled in GLX. This option disables direct rendering entirely. It can be useful on architectures where kernel DRM modules are not available. -
--enable-glx-tls+
--enable-glx-tlsEnable Thread Local Storage (TLS) in GLX. -
--with-expat=DIR- The DRI-enabled libGL uses expat to +
--with-expat=DIR- The DRI-enabled libGL uses expat to
parse the DRI configuration files in
/etc/drircand~/.drirc. This option allows a specific expat installation to be used. For example,--with-expat=/usr/localwill @@ -197,11 +205,12 @@ and/usr/local/lib, respectively.OSMesa
No libGL is built in this mode. Instead, the driver code is built into the Off-Screen Mesa (OSMesa) library. See the Off-Screen Rendering -page for more details. +page for more details. It corresponds to the option +
--enable-osmesa.-
-
--with-osmesa-bits=BITS+--with-osmesa-bits=BITSThis option allows the size of the color channel in bits to be specified. By default, an 8-bit channel will be used, and the driver will be named libOSMesa. Other @@ -219,31 +228,6 @@ libraries that will be built. More details on the specific GL libraries can be found in the basic installation instructions. -
-
-
- GLU
The libGLU library will be built by default -on all drivers. This can be disable with the option -
--disable-glu. -
4. Demo Program Options
- --There are many demonstration programs in the MesaDemos tarball. If the -programs are available when
./configureis run, a subset of -the programs will be built depending on the driver and library options -chosen. See the directoryprogsfor the full set of demos. - --
-
--with-demos=DEMOS,DEMOS,...-This option allows a -specific set of demo programs to be built. For example, -
--with-demos="xdemos,slang". Beware that if this option is -used, it will not be ensured that the necessary GL libraries will be -available. ---without-demosThis completely disables building the -demo programs. It is equivalent to
--with-demos=no. -