Lines Matching +full:- +full:- +full:with +full:- +full:dri +full:- +full:drivers
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dt…
4 <meta http-equiv="content-type" content="text/html; charset=utf-8">
24 <li><a href="#dri">DRI Driver Options</a></li>
44 --help</code>. If you are using a development snapshot and the configure
48 will run <code>configure</code> with these options after it is
64 Some of the generic autoconf options are used with Mesa:
67 <dt><code>--prefix=PREFIX</code></dt>
73 <dt><code>--exec-prefix=EPREFIX</code></dt>
75 where architecture-dependent files will be installed. In Mesa, this is
80 <dt><code>--libdir=LIBDIR</code></dt>
85 <code>--libdir=/usr/local/lib64</code> is used, the libraries will be
90 <dt><code>--sysconfdir=DIR</code></dt>
93 Currently there's only one config file provided when dri drivers are
94 enabled - it's <code>drirc</code>.</p>
97 <dt><code>--enable-static, --disable-shared</code></dt>
116 directories. For example, <code>LDFLAGS="-L/usr/X11R6/lib"</code>.</p>
121 <code>pkg-config</code> utility is a hard requirement for configuring and
124 path for <code>pkg-config</code>. For instance, setting
135 <dt><code>--enable-debug</code></dt>
142 <dt><code>--disable-asm</code></dt>
149 <dt><code>--build=</code></dt>
150 <dt><code>--host=</code></dt>
152 it's running on. In order to build cross-compile Mesa on a x86-64 machine
155 <p><code>--build=x86_64-pc-linux-gnu --host=i686-pc-linux-gnu</code></p>
158 information check with the
159 <a href="https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Specify…
167 further information -
168 <a href="https://gcc.gnu.org/onlinedocs/gcc/Submodel-Options.html"> gcc
174 <code>./configure CC="gcc -m32" CXX="g++ -m32" --build=x86_64-pc-linux-gnu --host=i686-pc-linux-gnu…
185 configure options <code>--enable-glx</code> and <code>--enable-osmesa</code>
190 to the option <code>--enable-glx=xlib</code> or <code>--enable-glx=gallium-xlib</code>.
192 <h3 id="dri">DRI</h3><p>This mode uses the DRI hardware drivers for
193 accelerated OpenGL rendering. To enable use <code>--enable-glx=dri
194 --enable-dri</code>.
196 <!-- DRI specific options -->
198 <dt><code>--with-dri-driverdir=DIR</code>
200 location the DRI drivers will be installed to and the location libGL
201 will search for DRI drivers. The default is <code>${libdir}/dri</code>.
202 <dt><code>--with-dri-drivers=DRIVER,DRIVER,...</code>
204 allows a specific set of DRI drivers to be built. For example,
205 <code>--with-dri-drivers="swrast,i965,radeon,nouveau"</code>. By
206 default, the drivers will be chosen depending on the target platform.
207 See the directory <code>src/mesa/drivers/dri</code> in the source tree
208 for available drivers. Beware that the swrast DRI driver is used by both
211 <!-- This explanation might be totally bogus. Kristian? -->
212 <dt><code>--disable-driglx-direct</code>
214 GLX. Normally, direct hardware rendering through the DRI drivers and
218 <dt><code>--enable-glx-tls</code> <dd><p>
221 <dt><code>--with-expat=DIR</code>
223 <p>The DRI-enabled libGL uses expat to
224 parse the DRI configuration files in <code>${sysconfdir}/drirc</code> and
226 to be used. For example, <code>--with-expat=/usr/local</code> will
232 mode. Instead, the driver code is built into the Off-Screen Mesa
233 (OSMesa) library. See the <a href="osmesa.html">Off-Screen Rendering</a>
235 <code>--enable-osmesa</code>.
237 <!-- OSMesa specific options -->
239 <dt><code>--with-osmesa-bits=BITS</code>
241 of the color channel in bits to be specified. By default, an 8-bit
243 options are 16- and 32-bit color channels, which will add the bit size
244 to the library name. For example, <code>--with-osmesa-bits=16</code>
245 will create the libOSMesa16 library with a 16-bit color channel.