X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=docs%2Finstall.html;h=e1018119a766bf74b03f6903f3db64509c5c15fa;hb=1df72402d99145425531297eef6772b88ce5225d;hp=3962ea5c91e12ace2584412944c6d754f1515223;hpb=f0f04cd12db156ec53b7ea46fae27199af121f90;p=mesa.git diff --git a/docs/install.html b/docs/install.html index 3962ea5c91e..e1018119a76 100644 --- a/docs/install.html +++ b/docs/install.html @@ -12,16 +12,16 @@
  1. Unix / X11
  2. Windows -
  3. SCons +
  4. Building with SCons
  5. Other

@@ -31,8 +31,22 @@

1. Unix/X11 Compilation and Installation

- -

1.1 Prerequisites for DRI and hardware acceleration

+
+

1.1 General prerequisites for building

+ + + + +
+

1.2 Prerequisites for DRI and hardware acceleration

The following are required for DRI-based hardware acceleration with Mesa: @@ -49,7 +63,7 @@ version 2.4.15 or later -

1.2 Building with Autoconf

+

1.3 Building with Autoconf

Mesa may be built using autoconf. @@ -59,7 +73,7 @@ If that fails the traditional Mesa build system is available. -

1.3 Building with traditional Makefiles

+

1.4 Building with traditional Makefiles

The traditional Mesa build system is based on a collection of pre-defined @@ -126,7 +140,7 @@ Later, if you want to rebuild for a different configuration run -

1.4 The libraries

+

1.5 The libraries

When compilation has finished, look in the top-level lib/ @@ -185,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

- -

-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. -

- -

-Before running a demo, you'll probably have to set two environment variables -to indicate where the libraries are located. For example: -

-

-cd lib/ -
-export LD_LIBRARY_PATH=${PWD} -
-export LIBGL_DRIVERS_PATH=${PWD} (if using DRI drivers) -
-

-Next, change to the Mesa/demos/ directory: +If you built with Gallium support, look in lib/gallium/ for Gallium-based +versions of libGL and device drivers.

-
-cd ../progs/demos -
-

-Run a demo such as gears: -

-
-./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: -

-
-ldd gears -
- -

-You should see something like this: -

-
-        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)
-
- -

-Retrace your steps if this doesn't look right. -

@@ -330,7 +274,6 @@ For example, compiling and linking a GLUT application can be done with:

Please see the instructions on building with SCons. -Alternatively see README.WIN32 file.