diff options
Diffstat (limited to 'docs/install.html')
| -rw-r--r-- | docs/install.html | 156 |
1 files changed, 81 insertions, 75 deletions
diff --git a/docs/install.html b/docs/install.html index 804dee59b5a..16ef013688a 100644 --- a/docs/install.html +++ b/docs/install.html @@ -21,10 +21,42 @@ <a name="unix-x11"> <H2>1. Unix/X11 Compilation and Installation</H1> -<h3>1.1 Compilation</h3> +<h3>1.1 Prerequisites for DRI and Hardware Acceleration</h3> + +<p> +To build Mesa 7.1 with DRI-based hardware acceleration you must first have +the <a href="http://dri.freedesktop.org/libdrm/" target="_parent">DRM version 2.3.1</a>. +</p> + +<p> +You should also be using the Xorg server version 1.4 or 1.5. +</p> + + + +<h3>1.2 Autoconf Compilation</h3> + +<p> +Mesa may be <a href="autoconf.html">built using autoconf</a>. +This should work well on most GNU-based systems. +When that fails, the traditional Mesa build system is available. + + + +<h3>1.3 Traditional Compilation</h3> + +<p> +The traditional Mesa build system is based on a collection of pre-defined +system configurations. +</p> <p> -Mesa may be compiled in several different ways: +To see the list of configurations, type <b>make</b> alone. +Then choose a configuration from the list and type <b>make configname</b>. +</p> + +<p> +Mesa may be built in several different ways using the predefined configurations: </p> <ul> <li><b><em>Stand-alone/Xlib mode</em></b> - Mesa will be compiled as @@ -49,62 +81,6 @@ accelerated OpenGL rendering (for ATI, Intel, Matrox, etc) will be built. The libGL.so library will support the GLX extension and will load/use the DRI hardware drivers. -<p> -<b>Prerequisites:</b> -</p> - -<ol> - -<li> -<p> -DRM kernel modules and header files from the -<a href="http://dri.sf.net/" target="_parent">DRI</a> project. -</p> - -<p> -If you don't already have the DRM file, you can get the sources from -CVS by doing: -<pre> -cvs -z3 -d:pserver:[email protected]:/cvs/dri co drm -</pre> -<p> -See the <a href="http://dri.freedesktop.org/wiki/Building" target="_parent"> -DRI Building Instructions</a> for the steps to build the DRM modules. Mesa -6.5 requires at least libdrm 2.0.1 or greater. -</p> -<p> -You can verify that the DRM files have been properly installed by -running <code>pkg-config --modversion libdrm</code> - -</li> - -<li> -Recent /usr/include/GL/glxproto.h file. -<p>You'll need this if you get any errors about _GLXvop_BindTexImageEXT -being undefined. -</p> -<p> -Download/install the -<a href="http://gitweb.freedesktop.org/?p=xorg/proto/glproto.git">glproto</a> -module from X.org git, or grab the -<A href="http://webcvs.freedesktop.org/*checkout*/xorg/proto/GL/glxproto.h?rev=1.9&content-type=text%2Fplain">glxproto.h file</a> and put it in the -Mesa/include/GL/ directory. -</p> - -</li> - -<li>DRI-enabled X server. -<p>Visit -<a href="http://www.xfree86.org" target="_parent">XFree86</a> -or -<a href="http://freedesktop.org/wiki/Software_2fXserver" target="_parent"> -X.org</a> -for more information. -</p> -</li> - -</ol> - <p> Build Mesa and the DRI hardware drivers by running @@ -117,8 +93,13 @@ There are also <code>linux-dri-x86</code>, <code>linux-dri-x86-64</code>, and <code>linux-ppc</code> configurations which are optimized for those architectures. </p> +<p> +Make sure you have the prerequisite versions of DRM and Xserver mentioned +above. +</p> </li> + </ul> @@ -128,7 +109,7 @@ Later, if you want to rebuild for a different configuration run </p> -<h3>1.2 The libraries</h3> +<h3>1.4 The libraries</h3> <p> When compilation has finished, look in the top-level <code>lib/</code> @@ -169,15 +150,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: </p> <pre> --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 @@ -188,7 +169,7 @@ If you built the DRI hardware drivers, you'll also see the DRI drivers: </pre> -<h3>1.3 Running the demos</h3> +<h3>1.5 Running the demos</h3> <p> If you downloaded/unpacked the MesaDemos-x.y.z.tar.gz archive or @@ -197,18 +178,15 @@ bunch of demonstration programs. </p> <p> -Before running a demo, you may have to set an environment variable -(such as <b>LD_LIBRARY_PATH</b> 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: <p> <blockquote> -<b>cd</b> into the Mesa <b>lib/</b> directory. +<b>cd lib/</b> <br> -<b>setenv LD_LIBRARY_PATH ${cwd}</b> (if using csh or tcsh shell) +<b>export LD_LIBRARY_PATH=${PWD}</b> <br> -or, -<br> -<b>export LD_LIBRARY_PATH=${PWD}</b> (if using bash or sh shell) +<b>export LIBGL_DRIVERS_PATH=${PWD}</b> (if using DRI drivers) </blockquote> <p> @@ -266,7 +244,7 @@ Retrace your steps if this doesn't look right. </p> -<H3>1.4 Installing the header and library files</H3> +<H3>1.6 Installing the header and library files</H3> <p> The standard location for the OpenGL header files on Unix-type systems is @@ -287,7 +265,15 @@ already installed, you'll have to choose different directories, like To install Mesa's headers and libraries, run <code>make install</code>. But first, check the Mesa/configs/default file and examine the values of the <b>INSTALL_DIR</b> and <b>DRI_DRIVER_INSTALL_DIR</b> variables. -Change them if needed, then run <code>make install</code> +Change them if needed, then run <code>make install</code>. +</p> + +<p> +The variable +<b>DESTDIR</b> may also be used to install the contents to a temporary +staging directory. +This can be useful for package management. +For example: <code>make install DESTDIR=/somepath/</code> </p> <p> @@ -298,6 +284,26 @@ This is a handy way to compare multiple OpenGL implementations. </p> +<H3>1.7 Building OpenGL Programs With pkg-config</H3> + +<p> +Running <code>make install</code> will install package configuration files +for the pkg-config utility. +</p> + +<p> +When compiling your OpenGL application you can use pkg-config to determine +the proper compiler and linker flags. +</p> + +<p> +For example, compiling and linking a GLUT application can be done with: +</p> +<pre> + gcc `pkg-config --cflags --libs glut` mydemo.c -o mydemo +</pre> + +<br> <a name="windows"> <H2>2. Windows Compilation and Installation</H1> |