-The following are required for DRI-based hardware acceleration with Mesa 7.3: +The following are required for DRI-based hardware acceleration with Mesa:
-
Mesa may be built using autoconf.
@@ -57,7 +73,7 @@ If that fails the traditional Mesa build system is available.
-
The traditional Mesa build system is based on a collection of pre-defined
@@ -124,7 +140,7 @@ Later, if you want to rebuild for a different configuration run
-
When compilation has finished, look in the top-level
-If you downloaded/unpacked the MesaDemos-x.y.z.tar.gz archive or
-obtained Mesa from CVS, the progs/ directory will contain a
-bunch of demonstration programs.
+If you built with Gallium support, look in lib/gallium/ for Gallium-based
+versions of libGL and device drivers.
-Before running a demo, you'll probably have to set two environment variables
-to indicate where the libraries are located. For example:
-
-
-Next, change to the Mesa/demos/ directory:
-
-Run a demo such as gears:
-
-If this doesn't work, try the Mesa/progs/xdemos/glxinfo program
-and see that it prints the expected Mesa version number.
-
-If you're using Linux or a similar OS, verify that the demo program is
-being linked with the proper library files:
-
-You should see something like this:
-
-Retrace your steps if this doesn't look right.
-
-Please see the README.WIN32 file.
+Please see the instructions on building with SCons.
+
+To build Mesa with SCons on Linux or Windows do
+
+The build output will be placed in
+build/platform-machine-debug/..., where platform is for
+example linux or windows, machine is x86 or x86_64, optionally followed
+by -debug for debug builds.
+To build Mesa with SCons for Windows on Linux using the MinGW crosscompiler toolchain do
+
+This will create:
+
+Put them all in the same directory to test them.
+
Documentation for other environments (some may be very out of date):
1.3 Building with traditional Makefiles
+1.4 Building with traditional Makefiles
1.4 The libraries
+1.5 The libraries
lib/
@@ -183,81 +199,11 @@ If you built the DRI hardware drivers, you'll also see the DRI drivers:
-rwxr-xr-x 1 brian users 10997120 Jul 21 12:13 unichrome_dri.so
-
-
-1.5 Running the demos
-
-cd lib/
-
-
-
-export LD_LIBRARY_PATH=${PWD}
-
-export LIBGL_DRIVERS_PATH=${PWD} (if using DRI drivers)
-
-cd ../progs/demos
-
-
-
-./gears
-
-
-
-ldd gears
-
-
-
- libglut.so.3 => /home/brian/Mesa/lib/libglut.so.3 (0x40013000)
- libGLU.so.1 => /home/brian/Mesa/lib/libGLU.so.1 (0x40051000)
- libGL.so.1 => /home/brian/Mesa/lib/libGL.so.1 (0x400e0000)
- libc.so.6 => /lib/i686/libc.so.6 (0x42000000)
- libm.so.6 => /lib/i686/libm.so.6 (0x403da000)
- libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x403fc000)
- libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x404da000)
- libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x404f1000)
- libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x40543000)
- libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x4054b000)
- libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x405fd000)
- libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40605000)
- libpthread.so.0 => /lib/i686/libpthread.so.0 (0x40613000)
- /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
- libdl.so.2 => /lib/libdl.so.2 (0x40644000)
- libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x40647000)
- libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x40650000)
-
-
-2. Windows Compilation and Installation
3. Building with SCons
+
+
+ scons
+
+
+ scons platform=windows toolchain=crossmingw machine=x86 statetrackers=mesa drivers=softpipe,trace winsys=gdi
+
+
+
+3. Other systems
+
4. Other systems