From 8bd70a7bbefe420dd696bfd6dc3b64d3dd17e884 Mon Sep 17 00:00:00 2001 From: Brian Paul Date: Tue, 27 May 2008 13:27:57 -0600 Subject: update, re-org build/install instructions --- docs/install.html | 126 +++++++++++++++++++++++++++--------------------------- 1 file changed, 64 insertions(+), 62 deletions(-) (limited to 'docs') diff --git a/docs/install.html b/docs/install.html index 10688d8ca8..30565a1dc4 100644 --- a/docs/install.html +++ b/docs/install.html @@ -21,16 +21,53 @@

1. Unix/X11 Compilation and Installation

-

1.1 Compilation

+ +

1.1 Prerequisites for DRI and Hardware Acceleration

+ +

+To build Mesa with DRI-based hardware acceleration you must first have +the right version of DRM. +

+ +

+For Mesa 7.1 a particular snapshot of +DRM from git is required: +

+ +
+git-clone git://anongit.freedesktop.org/git/mesa/drm
+git-checkout (XXXX HASH ID TBD)
+
+ + +

+You should also be using Xorg server version 1.4 +

+ + + +

1.2 Autoconf Compilation

+ +

+Mesa may be built using autoconf. +This should work well on most GNU-based systems. +When that fails, the traditional Mesa build system is available. + + + +

1.3 Traditional Compilation

+ +

+The traditional Mesa build system is based on a collection of pre-defined +system configurations. +

+

+To see the list of configurations, type make alone. +Then choose a configuration from the list and type make configname. +

-Mesa is built by reading Makefile stubs from the configs directory. -There are configurations for many Unix variants and different Mesa -options. Type make from the top-level directory to see a list of -supported system configurations. Alternatively, an autoconf system can -be used to create a Makefile stub for your system. See the autoconf instructions for more details. Mesa -may be compiled in several ways using the predefined configurations: +Mesa may be built in several different ways using the predefined configurations:

@@ -115,7 +120,7 @@ Later, if you want to rebuild for a different configuration run

-

1.2 The libraries

+

1.4 The libraries

When compilation has finished, look in the top-level lib/ @@ -156,15 +161,15 @@ lrwxrwxrwx 1 brian users 23 Mar 26 07:53 libOSMesa.so.6 -> libOSM If you built the DRI hardware drivers, you'll also see the DRI drivers: 

--rwxr-xr-x   1 brian users 15607851 Jul 21 12:11 ffb_dri.so*
--rwxr-xr-x   1 brian users 15148747 Jul 21 12:11 i810_dri.so*
--rwxr-xr-x   1 brian users 14497814 Jul 21 12:11 i830_dri.so*
--rwxr-xr-x   1 brian users 16895413 Jul 21 12:11 i915_dri.so*
+-rwxr-xr-x   1 brian users 15607851 Jul 21 12:11 ffb_dri.so
+-rwxr-xr-x   1 brian users 15148747 Jul 21 12:11 i810_dri.so
+-rwxr-xr-x   1 brian users 14497814 Jul 21 12:11 i830_dri.so
+-rwxr-xr-x   1 brian users 16895413 Jul 21 12:11 i915_dri.so
 -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 16050488 Jul 21 12:11 r300_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
 -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
@@ -175,7 +180,7 @@ If you built the DRI hardware drivers, you'll also see the DRI drivers:
-

1.3 Running the demos

+

1.5 Running the demos

If you downloaded/unpacked the MesaDemos-x.y.z.tar.gz archive or @@ -184,18 +189,15 @@ bunch of demonstration programs.

-Before running a demo, you may have to set an environment variable -(such as LD_LIBRARY_PATH on Linux) to indicate where the -libraries are located. For example: +Before running a demo, you'll probably have to set two environment variables +to indicate where the libraries are located. For example:

-cd into the Mesa lib/ directory. -
-setenv LD_LIBRARY_PATH ${cwd} (if using csh or tcsh shell) +cd lib/
-or, +export LD_LIBRARY_PATH=${PWD}
-export LD_LIBRARY_PATH=${PWD} (if using bash or sh shell) +export LIBGL_DRIVERS_PATH=${PWD} (if using DRI drivers)

@@ -253,7 +255,7 @@ Retrace your steps if this doesn't look right.

-

1.4 Installing the header and library files

+

1.6 Installing the header and library files

The standard location for the OpenGL header files on Unix-type systems is @@ -293,7 +295,7 @@ This is a handy way to compare multiple OpenGL implementations.

-

1.5 pkg-config support

+

1.7 Building OpenGL Programs With pkg-config

Running make install will install package configuration files -- cgit v1.2.3