-Mesa uses a rather conventional Makefile system. -A GNU autoconf/automake system used to be included, but was discarded -in Mesa 5.1 because: -
--If someone strongly feels that Mesa should have a autoconf/automake -system and wants to contribute one and maintain it, we'll consider -adding it again. -
- -
-In Mesa 6.1 we modified the conventional Makefile system.
-Instead of specifying all the various system configurations in the
-Make-config file, there's a directory named configs/ which
-has an individual file for each configuration.
-One of the configs gets copied to configs/current, which
-is then included by all Makefiles.
-
-Note: if you've obtained Mesa through CVS, do this first: +Mesa may be compiled in several different ways:
-- cd Mesa - chmod a+x bin/mklib -- +
-Just type make in the top-level directory. +To compile stand-alone Mesa type make in the top-level directory. You'll see a list of supported system configurations. Choose one from the list (such as linux-x86), and type:
make linux-x86
+This will produce libGL.so and several other libraries
+-If you want to rebuild for a different configuration run +To build the DRI drivers you'll first need to have the DRM (Direct +Rendering Manager) kernel drivers and header files. +They're available from the DRI project. +
++You can get them from CVS by doing: +
+cvs -d:pserver:anonymous@pds.freedesktop.org:/cvs/dri login +(hit enter when prompted for a password) +cvs -z3 -d:pserver:anonymous@pdx.freedesktop.org:/cvs/dri co drm ++
+Make note of the directory in which the drm files are placed. +
++See the +DRI Building Instructions for the steps to build the DRM modules. +
+
+Next, in the Mesa-x.y.z/configs/default file, set the
+DRM_SOURCE_PATH variable to indicate where the DRM files
+are located.
+
+Now build Mesa and the DRI drivers by running +
++make linux-dri ++
+There are also linux-dri-x86, linux-dri-x86-64,
+and linux-ppc configurations, optimized for those architectures.
+
+Finally, you'll need a DRI-enabled X server from + +X.org or XFree86. +Visit those projects' home pages for more information. +
+ +
+Later, if you want to rebuild for a different configuration run
make realclean before rebuilding.
-When compilation has finished, look in the top-level lib/ directory.
+When compilation has finished, look in the top-level lib/
+directory.
You'll see a set of library files similar to this:
@@ -108,6 +133,23 @@ lrwxrwxrwx 1 brian users 23 Mar 26 07:53 libOSMesa.so.6 -> libOSM libOSMesa is the OSMesa (Off-Screen) interface library. ++If you built the DRI hardware drivers, you'll also see the DRI drivers: +
++-rwxr-xr-x 1 brian users 11320803 Jul 21 12:11 mach64_dri.so +-rwxr-xr-x 1 brian users 11418014 Jul 21 12:12 mga_dri.so +-rwxr-xr-x 1 brian users 11064426 Jul 21 12:12 r128_dri.so +-rwxr-xr-x 1 brian users 11849858 Jul 21 12:12 r200_dri.so +-rwxr-xr-x 1 brian users 11757388 Jul 21 12:12 radeon_dri.so +-rwxr-xr-x 1 brian users 11232304 Jul 21 12:13 s3v_dri.so +-rwxr-xr-x 1 brian users 11062970 Jul 21 12:13 savage_dri.so +-rwxr-xr-x 1 brian users 11214212 Jul 21 12:13 sis_dri.so +-rwxr-xr-x 1 brian users 11368736 Jul 21 12:13 tdfx_dri.so +-rwxr-xr-x 1 brian users 10598868 Jul 21 12:13 trident_dri.so +-rwxr-xr-x 1 brian users 10997120 Jul 21 12:13 unichrome_dri.so ++1.3 Running the demos