docs: Clean up autoconf.html.
Remove long dead options and clarify some things. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=69148 Reviewed-by: Brian Paul <brianp@vmware.com>
This commit is contained in:
parent
bd77f51758
commit
66be7b4c27
|
@ -123,24 +123,6 @@ directories.</p>
|
||||||
There are also a few general options for altering the Mesa build:
|
There are also a few general options for altering the Mesa build:
|
||||||
</p>
|
</p>
|
||||||
<dl>
|
<dl>
|
||||||
<dt><code>--with-x</code></dt>
|
|
||||||
<dd><p>When the X11 development libraries are
|
|
||||||
needed, the <code>pkg-config</code> utility <a href="#pkg-config">will
|
|
||||||
be used</a> for locating them. If they cannot be found through
|
|
||||||
<code>pkg-config</code> a fallback routing using <code>imake</code> will
|
|
||||||
be used. In this case, the <code>--with-x</code>,
|
|
||||||
<code>--x-includes</code> and <code>--x-libraries</code> options can
|
|
||||||
control the use of X for Mesa.</p>
|
|
||||||
</dd>
|
|
||||||
|
|
||||||
<dt><code>--enable-gl-osmesa</code></dt>
|
|
||||||
<dd><p>The <a href="osmesa.html">OSMesa
|
|
||||||
library</a> can be built on top of libGL for drivers that provide it.
|
|
||||||
This option controls whether to build libOSMesa. By default, this is
|
|
||||||
enabled for the Xlib driver and disabled otherwise. Note that this
|
|
||||||
option is different than using OSMesa as the driver.</p>
|
|
||||||
</dd>
|
|
||||||
|
|
||||||
<dt><code>--enable-debug</code></dt>
|
<dt><code>--enable-debug</code></dt>
|
||||||
<dd><p>This option will enable compiler
|
<dd><p>This option will enable compiler
|
||||||
options and macros to aid in debugging the Mesa libraries.</p>
|
options and macros to aid in debugging the Mesa libraries.</p>
|
||||||
|
@ -155,12 +137,12 @@ assembly will not be used.</p>
|
||||||
|
|
||||||
<dt><code>--enable-32-bit</code></dt>
|
<dt><code>--enable-32-bit</code></dt>
|
||||||
<dt><code>--enable-64-bit</code></dt>
|
<dt><code>--enable-64-bit</code></dt>
|
||||||
<dd><p>By default, the
|
<dd><p>By default, the build will compile code as directed by the environment
|
||||||
build will compile code as directed by the environment variables
|
variables
|
||||||
<code>CC</code>, <code>CFLAGS</code>, etc. If the compiler is
|
<code>CC</code>, <code>CFLAGS</code>, etc. If the compiler is
|
||||||
<code>gcc</code>, these options offer a helper to add the compiler flags
|
<code>gcc</code>, these options offer a helper to add the compiler flags
|
||||||
to force 32- or 64-bit code generation as used on the x86 and x86_64
|
to force 32- or 64-bit code generation as used on the x86 and x86_64
|
||||||
architectures.</p>
|
architectures. Note that these options are mutually exclusive.</p>
|
||||||
</dd>
|
</dd>
|
||||||
</dl>
|
</dl>
|
||||||
|
|
||||||
|
@ -171,19 +153,19 @@ architectures.</p>
|
||||||
There are several different driver modes that Mesa can use. These are
|
There are several different driver modes that Mesa can use. These are
|
||||||
described in more detail in the <a href="install.html">basic
|
described in more detail in the <a href="install.html">basic
|
||||||
installation instructions</a>. The Mesa driver is controlled through the
|
installation instructions</a>. The Mesa driver is controlled through the
|
||||||
configure option --with-driver. There are currently three supported
|
configure options <code>--enable-xlib-glx</code>, <code>--enable-osmesa</code>,
|
||||||
options in the configure script.
|
and <code>--enable-dri</code>.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<h3 id="xlib">Xlib</h3><p>This is the default mode for building Mesa.
|
<h3 id="xlib">Xlib</h3><p>
|
||||||
It uses Xlib as a software renderer to do all rendering. It corresponds
|
It uses Xlib as a software renderer to do all rendering. It corresponds
|
||||||
to the option <code>--with-driver=xlib</code>. The libX11 and libXext
|
to the option <code>--enable-xlib-glx</code>. The libX11 and libXext
|
||||||
libraries, as well as the X11 development headers, will be need to
|
libraries, as well as the X11 development headers, will be need to
|
||||||
support the Xlib driver.
|
support the Xlib driver.
|
||||||
|
|
||||||
<h3 id="dri">DRI</h3><p>This mode uses the DRI hardware drivers for
|
<h3 id="dri">DRI</h3><p>This mode uses the DRI hardware drivers for
|
||||||
accelerated OpenGL rendering. Enable the DRI drivers with the option
|
accelerated OpenGL rendering. Enable the DRI drivers with the option
|
||||||
<code>--with-driver=dri</code>. See the <a href="install.html">basic
|
<code>--enable-dri</code>. See the <a href="install.html">basic
|
||||||
installation instructions</a> for details on prerequisites for the DRI
|
installation instructions</a> for details on prerequisites for the DRI
|
||||||
drivers.
|
drivers.
|
||||||
|
|
||||||
|
@ -223,7 +205,8 @@ and <code>/usr/local/lib</code>, respectively.
|
||||||
<h3 id="osmesa">OSMesa </h3><p> No libGL is built in this
|
<h3 id="osmesa">OSMesa </h3><p> No libGL is built in this
|
||||||
mode. Instead, the driver code is built into the Off-Screen Mesa
|
mode. Instead, the driver code is built into the Off-Screen Mesa
|
||||||
(OSMesa) library. See the <a href="osmesa.html">Off-Screen Rendering</a>
|
(OSMesa) library. See the <a href="osmesa.html">Off-Screen Rendering</a>
|
||||||
page for more details.
|
page for more details. It corresponds to the option
|
||||||
|
<code>--enable-osmesa</code>.
|
||||||
|
|
||||||
<!-- OSMesa specific options -->
|
<!-- OSMesa specific options -->
|
||||||
<dl>
|
<dl>
|
||||||
|
|
Loading…
Reference in New Issue