From: Brian Paul
The following are required for DRI-based hardware acceleration with Mesa:
Compiling and Installing
-
-
-
-
-
-
-
-1. Unix/X11 Compilation and Installation
-
1.1 General prerequisites for building
+1. Prerequisites for building
+1.1 General
1.2 Prerequisites for DRI and hardware acceleration
+1.2 For DRI and hardware acceleration
@@ -78,22 +73,69 @@ the needed dependencies:
+
-
+The primary method to build Mesa on Unix systems is with autoconf.
+
-Mesa may be built using autoconf.
-This should work well on most GNU-based systems.
-If that fails the traditional Mesa build system is available.
+The general approach is the standard:
+1.3 Building with Autoconf
+2. Building with autoconf (Linux/Unix/X11)
+
+
+ ./configure
+ make
+ sudo make install
+
+But please read the detailed autoconf instructions
+for more details.
+
-The traditional Mesa build system is based on a collection of pre-defined +To build Mesa with SCons on Linux or Windows do +
++ scons ++
+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 +
++ scons platform=windows toolchain=crossmingw machine=x86 mesagdi libgl-gdi ++
+This will create: +
++Put them all in the same directory to test them. +
+ + + + ++The legacy Mesa build system is based on a collection of pre-defined system configurations. +Some of these might work for older systems not supported by autoconf.
To see the list of configurations, just type make
.
@@ -144,8 +186,6 @@ Make sure you have the prerequisite versions of DRM and Xserver mentioned
above.
-When compilation has finished, look in the top-level lib/
-(or lib64/
) directory.
-You'll see a set of library files similar to this:
-
-lrwxrwxrwx 1 brian users 10 Mar 26 07:53 libGL.so -> libGL.so.1* -lrwxrwxrwx 1 brian users 19 Mar 26 07:53 libGL.so.1 -> libGL.so.1.5.060100* --rwxr-xr-x 1 brian users 3375861 Mar 26 07:53 libGL.so.1.5.060100* -lrwxrwxrwx 1 brian users 11 Mar 26 07:53 libGLU.so -> libGLU.so.1* -lrwxrwxrwx 1 brian users 20 Mar 26 07:53 libGLU.so.1 -> libGLU.so.1.3.060100* --rwxr-xr-x 1 brian users 549269 Mar 26 07:53 libGLU.so.1.3.060100* -lrwxrwxrwx 1 brian users 12 Mar 26 07:53 libglut.so -> libglut.so.3* -lrwxrwxrwx 1 brian users 16 Mar 26 07:53 libglut.so.3 -> libglut.so.3.7.1* --rwxr-xr-x 1 brian users 597754 Mar 26 07:53 libglut.so.3.7.1* -lrwxrwxrwx 1 brian users 14 Mar 26 07:53 libOSMesa.so -> libOSMesa.so.6* -lrwxrwxrwx 1 brian users 23 Mar 26 07:53 libOSMesa.so.6 -> libOSMesa.so.6.1.060100* --rwxr-xr-x 1 brian users 23871 Mar 26 07:53 libOSMesa.so.6.1.060100* -- -
-libGL is the main OpenGL library (i.e. Mesa).
-
-libGLU is the OpenGL Utility library.
-
-libglut is the GLUT library.
-
-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 16895413 Jul 21 12:11 i915_dri.so --rwxr-xr-x 1 brian users 11849858 Jul 21 12:12 r200_dri.so --rwxr-xr-x 1 brian users 16050488 Jul 21 12:11 r300_dri.so --rwxr-xr-x 1 brian users 11757388 Jul 21 12:12 radeon_dri.so -- -
-If you built with Gallium support, look in lib/gallium/ for Gallium-based -versions of libGL and device drivers. -
- - -The standard location for the OpenGL header files on Unix-type systems is @@ -246,85 +237,89 @@ This is a handy way to compare multiple OpenGL implementations.
- -
-Running make install
will install package configuration files
-for the pkg-config utility.
-
-When compiling your OpenGL application you can use pkg-config to determine -the proper compiler and linker flags. -
+ +-For example, compiling and linking a GLUT application can be done with: +Documentation for other environments (some may be very out of date):
-- gcc `pkg-config --cflags --libs glut` mydemo.c -o mydemo -- -
-Please see the instructions on building with SCons. -
+
-To build Mesa with SCons on Linux or Windows do
+When compilation has finished, look in the top-level lib/
+(or lib64/
) directory.
+You'll see a set of library files similar to this:
- scons +lrwxrwxrwx 1 brian users 10 Mar 26 07:53 libGL.so -> libGL.so.1* +lrwxrwxrwx 1 brian users 19 Mar 26 07:53 libGL.so.1 -> libGL.so.1.5.060100* +-rwxr-xr-x 1 brian users 3375861 Mar 26 07:53 libGL.so.1.5.060100* +lrwxrwxrwx 1 brian users 11 Mar 26 07:53 libGLU.so -> libGLU.so.1* +lrwxrwxrwx 1 brian users 20 Mar 26 07:53 libGLU.so.1 -> libGLU.so.1.3.060100* +-rwxr-xr-x 1 brian users 549269 Mar 26 07:53 libGLU.so.1.3.060100* +lrwxrwxrwx 1 brian users 14 Mar 26 07:53 libOSMesa.so -> libOSMesa.so.6* +lrwxrwxrwx 1 brian users 23 Mar 26 07:53 libOSMesa.so.6 -> libOSMesa.so.6.1.060100* +-rwxr-xr-x 1 brian users 23871 Mar 26 07:53 libOSMesa.so.6.1.060100*+
-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.
+libGL is the main OpenGL library (i.e. Mesa).
+
+libGLU is the OpenGL Utility library.
+
+libOSMesa is the OSMesa (Off-Screen) interface library.
-To build Mesa with SCons for Windows on Linux using the MinGW crosscompiler toolchain do +If you built the DRI hardware drivers, you'll also see the DRI drivers:
- scons platform=windows toolchain=crossmingw machine=x86 mesagdi libgl-gdi +-rwxr-xr-x 1 brian users 16895413 Jul 21 12:11 i915_dri.so +-rwxr-xr-x 1 brian users 16895413 Jul 21 12:11 i965_dri.so +-rwxr-xr-x 1 brian users 11849858 Jul 21 12:12 r200_dri.so +-rwxr-xr-x 1 brian users 16050488 Jul 21 12:11 r300_dri.so +-rwxr-xr-x 1 brian users 11757388 Jul 21 12:12 radeon_dri.so+
-This will create: -
--Put them all in the same directory to test them. +If you built with Gallium support, look in lib/gallium/ for Gallium-based +versions of libGL and device drivers.
- -
-Documentation for other environments (some may be very out of date):
+Running make install
will install package configuration files
+for the pkg-config utility.
+When compiling your OpenGL application you can use pkg-config to determine +the proper compiler and linker flags. +
++For example, compiling and linking a GLUT application can be done with: +
++ gcc `pkg-config --cflags --libs glut` mydemo.c -o mydemo ++