From: Chia-I Wu
- $ ./configure --enable-gles2 --enable-openvg --enable-gallium-nouveau + $ ./configure --enable-gles1 --enable-gles2 \ + --with-dri-drivers=... \ + --with-gallium-drivers=...-
The main library and OpenGL is enabled by default. The first option above -enables OpenGL ES 2.x. The second option enables -OpenVG.
+The main library and OpenGL is enabled by default. The first two options +above enables OpenGL ES 1.x and 2.x. The last two +options enables the listed classic and and Gallium drivers respectively.
@@ -42,8 +44,8 @@ enables OpenGL ES 2.x. The second option enablesIn the given example, it will build and install libEGL
,
-libGL
, libGLESv1_CM
, libGLESv2
,
-libOpenVG
, and one or more EGL drivers.
libGL
, libGLESv1_CM
, libGLESv2
, and one
+or more EGL drivers.
${libdir}/egl
.
+--enable-gallium-egl
+
+Enable the optional egl_gallium
driver.
--with-egl-platforms
List the platforms (window systems) to support. Its argument is a comma @@ -88,15 +96,17 @@ internal library that supports multiple APIs.
--enable-openvg
+--enable-shared-glapi
-OpenVG must be explicitly enabled by this option.
+By default, libGL
has its own copy of libglapi
.
+This options makes libGL
use the shared libglapi
. This
+is required if applications mix OpenGL and OpenGL ES.
--enable-gallium-egl
+--enable-openvg
-Explicitly enable or disable egl_gallium
.
OpenVG must be explicitly enabled by this option.
Generally, egl_dri2
is preferred over egl_gallium
when the system already has DRI drivers. As egl_gallium
is loaded
before egl_dri2
when both are available, egl_gallium
-may either be disabled with --disable-gallium-egl
or packaged
-separately.
EGLDisplay
without going through the EGL APIs, the driver
should as well lock the display before using it.
-libGL.so
, libGLESv1_CM.so
, and
-libGLESv2.so
should an application link to? Bad things may happen
-when, say, an application is linked to libGLESv2.so
and
-libcairo
, which is linked to libGL.so
instead.