X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;ds=sidebyside;f=docs%2Finstall.html;h=e1018119a766bf74b03f6903f3db64509c5c15fa;hb=c108a3f863c44b5e9760d4668148ef8ca7557b2f;hp=16ef013688aaa3a04b8a9e3b87229142b25159d8;hpb=a8d1521f30766b6a4707aa9966e1f2f9c0b3ac00;p=mesa.git diff --git a/docs/install.html b/docs/install.html index 16ef013688a..e1018119a76 100644 --- a/docs/install.html +++ b/docs/install.html @@ -1,58 +1,88 @@ -
-To build Mesa 7.1 with DRI-based hardware acceleration you must first have -the DRM version 2.3.1. -
+ + +-You should also be using the Xorg server version 1.4 or 1.5. +The following are required for DRI-based hardware acceleration with Mesa:
+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. +If that fails the traditional Mesa build system is available. -
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.
+To see the list of configurations, just type make
.
+Then choose a configuration from the list and type make
+configname.
@@ -66,7 +96,7 @@ allow you to run OpenGL/GLX applications on any X server (regardless of whether it supports the GLX X server extension). You will not be able to use hardware 3D acceleration.
-To compile stand-alone Mesa 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:
When compilation has finished, look in the top-level lib/
@@ -168,82 +199,14 @@ 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
-
-
-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. -
+@@ -284,7 +247,8 @@ This is a handy way to compare multiple OpenGL implementations.
-
Running make install
will install package configuration files
@@ -309,20 +273,46 @@ For example, compiling and linking a GLUT application can be done with:
-Please see the README.WIN32 file. +Please see the instructions on building with SCons.
- - --Please see the README.VMS file. +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 statetrackers=mesa drivers=softpipe,trace winsys=gdi ++
+This will create: +
++Put them all in the same directory to test them. +
@@ -333,6 +323,7 @@ Documentation for other environments (some may be very out of date):