Marten van der Honing wrote:
Hello,
Is mesa linux-directfb software only, or does it support dri also?
Thanks for your answers in advance.
Greetings,
M van der Honing
Software only, actually.
--
Regards,
Claudio Ciccani
[EMAIL PROTECTED]
http://directfb.org
The user can request specific demos directories to build in. For
example:
./configure --with-demos=demos,xdemos
The drawback is that we don't check for the necessary libararies in
that case, only that the directory in progs/ exists.
---
configure.ac | 43
Report some of the common settings back to the user after configure
has completed.
---
configure.ac | 44
1 files changed, 44 insertions(+), 0 deletions(-)
diff --git a/configure.ac b/configure.ac
index c639378..94fb9e3 100644
--- a/configure.ac
+++
Allow the user to specify that they want static libraries through the
--{enable,disable}-{static,shared} switches like libtool. The mesa build
only allows for one at a time, so static will be chosen if someone has
passed --enable-static or --disable-shared.
This also allows the mklib options to
Added autoconf bits to allow using DRI as the driver through the option
--with-dri-driver=DRIVER. The options are x11 (default) and dri. Three
DRI specific options for controlling the driver directory, direct
rendering and TLS are also added.
The DRI will probably not work for platforms besides
Added autoconf support for using OSMesa as the driver instead linking
it to libGL. This is enabled through --with-driver=osmesa.
To differentiate these cases, another option --enable-x11-osmesa is used
to enable or disable building OSMesa when the driver is x11.
---
configure.ac | 76
Allow the user to specify channel bits of 16 or 32 to enable OSMesa16 or
OSMesa32 instead of the default OSMesa. This option is controlled
through the option --with-osmesa-bits=BITS and is only honored when the
driver is osmesa.
The osdemos are not enabled in the 16 or 32 bit case because the
The user can request specific DRI drivers to build rather than the
default of all that build on this platform. This allows the list of
drivers to be easily slimmed down.
This is controlled through the option --with-dri-drivers. For example:
./configure --with-driver=dri
This adds the initial support for using autoconf configuration. Support
is available for shared Xlib driver builds. Later this will be extended
to dri and osmesa-only builds and possibly targetting non-X backends.
Support for static library builds will also be added.
The configure script fills in
