blob: bc21c6c4894fc9fcc2537e9561f97209f805f701 [file] [log] [blame]
Andreas Bollecd5c7c2012-06-12 09:05:03 +02001<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
2<html lang="en">
3<head>
4 <meta http-equiv="content-type" content="text/html; charset=utf-8">
5 <title>Mesa EGL</title>
6 <link rel="stylesheet" type="text/css" href="mesa.css">
7</head>
Chia-I Wuada46052010-01-21 15:29:14 +08008<body>
9
Andreas Bollb5da52a2012-09-18 18:57:02 +020010<div class="header">
11 <h1>The Mesa 3D Graphics Library</h1>
12</div>
13
14<iframe src="contents.html"></iframe>
15<div class="content">
16
Chia-I Wuada46052010-01-21 15:29:14 +080017<h1>Mesa EGL</h1>
18
19<p>The current version of EGL in Mesa implements EGL 1.4. More information
20about EGL can be found at
Andreas Bolla73c59b2012-09-18 19:31:28 +020021<a href="http://www.khronos.org/egl/">
Brian Paulaeff9f92010-01-21 08:13:32 -070022http://www.khronos.org/egl/</a>.</p>
Chia-I Wuada46052010-01-21 15:29:14 +080023
24<p>The Mesa's implementation of EGL uses a driver architecture. The main
25library (<code>libEGL</code>) is window system neutral. It provides the EGL
26API entry points and helper functions for use by the drivers. Drivers are
27dynamically loaded by the main library and most of the EGL API calls are
28directly dispatched to the drivers.</p>
29
Chia-I Wu65e8f812010-12-25 02:45:13 +080030<p>The driver in use decides the window system to support.</p>
Chia-I Wuada46052010-01-21 15:29:14 +080031
32<h2>Build EGL</h2>
33
34<ol>
35<li>
Chia-I Wu3418f742010-11-02 23:55:56 +080036<p>Run <code>configure</code> with the desired client APIs and enable
37the driver for your hardware. For example</p>
Chia-I Wuada46052010-01-21 15:29:14 +080038
39<pre>
Chia-I Wu8eea0502011-06-20 11:14:56 +090040 $ ./configure --enable-gles1 --enable-gles2 \
41 --with-dri-drivers=... \
42 --with-gallium-drivers=...
Chia-I Wuada46052010-01-21 15:29:14 +080043</pre>
44
Chia-I Wu8eea0502011-06-20 11:14:56 +090045<p>The main library and OpenGL is enabled by default. The first two options
46above enables <a href="opengles.html">OpenGL ES 1.x and 2.x</a>. The last two
47options enables the listed classic and and Gallium drivers respectively.</p>
Chia-I Wuc6320c52010-10-28 17:25:07 +080048
Chia-I Wuada46052010-01-21 15:29:14 +080049</li>
50
51<li>Build and install Mesa as usual.</li>
52</ol>
53
54<p>In the given example, it will build and install <code>libEGL</code>,
Chia-I Wu8eea0502011-06-20 11:14:56 +090055<code>libGL</code>, <code>libGLESv1_CM</code>, <code>libGLESv2</code>, and one
56or more EGL drivers.</p>
Chia-I Wuada46052010-01-21 15:29:14 +080057
58<h3>Configure Options</h3>
59
60<p>There are several options that control the build of EGL at configuration
61time</p>
62
Andreas Boll76d4f9e2012-09-20 16:01:08 +020063<dl>
64<dt><code>--enable-egl</code></dt>
65<dd>
Chia-I Wuada46052010-01-21 15:29:14 +080066
67<p>By default, EGL is enabled. When disabled, the main library and the drivers
68will not be built.</p>
69
Andreas Boll76d4f9e2012-09-20 16:01:08 +020070</dd>
Chia-I Wuada46052010-01-21 15:29:14 +080071
Andreas Boll76d4f9e2012-09-20 16:01:08 +020072<dt><code>--with-egl-driver-dir</code></dt>
73<dd>
Chia-I Wua6342af2010-01-26 10:54:45 +080074
75<p>The directory EGL drivers should be installed to. If not specified, EGL
76drivers will be installed to <code>${libdir}/egl</code>.</p>
77
Andreas Boll76d4f9e2012-09-20 16:01:08 +020078</dd>
Chia-I Wua6342af2010-01-26 10:54:45 +080079
Andreas Boll76d4f9e2012-09-20 16:01:08 +020080<dt><code>--with-egl-platforms</code></dt>
81<dd>
Chia-I Wuada46052010-01-21 15:29:14 +080082
Chia-I Wub365b152010-07-03 17:18:40 +080083<p>List the platforms (window systems) to support. Its argument is a comma
Nathan Kidd0691b372014-01-03 16:44:00 -070084separated string such as <code>--with-egl-platforms=x11,drm</code>. It decides
Chia-I Wub365b152010-07-03 17:18:40 +080085the platforms a driver may support. The first listed platform is also used by
86the main library to decide the native platform: the platform the EGL native
87types such as <code>EGLNativeDisplayType</code> or
88<code>EGLNativeWindowType</code> defined for.</p>
Chia-I Wuada46052010-01-21 15:29:14 +080089
Chia-I Wue7424d72010-09-19 16:54:39 +080090<p>The available platforms are <code>x11</code>, <code>drm</code>,
Emil Velikovb0a92992015-07-10 00:16:21 +010091<code>wayland</code>, <code>surfaceless</code>, <code>android</code>,
92and <code>haiku</code>. The <code>android</code> platform
Emil Velikov55029b22015-03-14 22:36:29 +000093can only be built as a system component, part of AOSP, while the
Emil Velikovb0a92992015-07-10 00:16:21 +010094<code>haiku</code> platform can only be built with SCons.
Emil Velikov55029b22015-03-14 22:36:29 +000095Unless for special needs, the build system should
Chia-I Wu3418f742010-11-02 23:55:56 +080096select the right platforms automatically.</p>
Chia-I Wu2e3c4e42010-05-07 14:13:08 +080097
Andreas Boll76d4f9e2012-09-20 16:01:08 +020098</dd>
Chia-I Wu2e3c4e42010-05-07 14:13:08 +080099
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200100<dt><code>--enable-gles1</code></dt>
101<dt><code>--enable-gles2</code></dt>
102<dd>
Chia-I Wu2e3c4e42010-05-07 14:13:08 +0800103
Chia-I Wu65e8f812010-12-25 02:45:13 +0800104<p>These options enable OpenGL ES support in OpenGL. The result is one big
105internal library that supports multiple APIs.</p>
Chia-I Wuada46052010-01-21 15:29:14 +0800106
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200107</dd>
Chia-I Wua1306f42010-01-22 15:51:51 +0800108
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200109<dt><code>--enable-shared-glapi</code></dt>
110<dd>
Chia-I Wuc6320c52010-10-28 17:25:07 +0800111
Chia-I Wu8eea0502011-06-20 11:14:56 +0900112<p>By default, <code>libGL</code> has its own copy of <code>libglapi</code>.
113This options makes <code>libGL</code> use the shared <code>libglapi</code>. This
114is required if applications mix OpenGL and OpenGL ES.</p>
Chia-I Wuc6320c52010-10-28 17:25:07 +0800115
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200116</dd>
Chia-I Wuc6320c52010-10-28 17:25:07 +0800117
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200118</dl>
Chia-I Wuada46052010-01-21 15:29:14 +0800119
Chia-I Wuada46052010-01-21 15:29:14 +0800120<h2>Use EGL</h2>
121
Chia-I Wu411bba32010-06-11 12:47:14 +0800122<h3>Demos</h3>
Chia-I Wuada46052010-01-21 15:29:14 +0800123
Chia-I Wu411bba32010-06-11 12:47:14 +0800124<p>There are demos for the client APIs supported by EGL. They can be found in
125mesa/demos repository.</p>
Chia-I Wuada46052010-01-21 15:29:14 +0800126
127<h3>Environment Variables</h3>
128
129<p>There are several environment variables that control the behavior of EGL at
130runtime</p>
131
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200132<dl>
133<dt><code>EGL_DRIVERS_PATH</code></dt>
134<dd>
Chia-I Wu5d8646c2010-02-02 15:34:55 +0800135
136<p>By default, the main library will look for drivers in the directory where
137the drivers are installed to. This variable specifies a list of
138colon-separated directories where the main library will look for drivers, in
Chia-I Wu6fd8b6a2010-02-02 16:47:53 +0800139addition to the default directory. This variable is ignored for setuid/setgid
140binaries.</p>
Chia-I Wu5d8646c2010-02-02 15:34:55 +0800141
Chia-I Wucba77862011-01-04 00:53:19 +0800142<p>This variable is usually set to test an uninstalled build. For example, one
143may set</p>
144
145<pre>
146 $ export LD_LIBRARY_PATH=$mesa/lib
147 $ export EGL_DRIVERS_PATH=$mesa/lib/egl
148</pre>
149
150<p>to test a build without installation</p>
151
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200152</dd>
Chia-I Wu5d8646c2010-02-02 15:34:55 +0800153
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200154<dt><code>EGL_DRIVER</code></dt>
155<dd>
Chia-I Wuada46052010-01-21 15:29:14 +0800156
Chia-I Wuc98ea262011-01-07 16:30:08 +0800157<p>This variable specifies a full path to or the name of an EGL driver. It
158forces the specified EGL driver to be loaded. It comes in handy when one wants
159to test a specific driver. This variable is ignored for setuid/setgid
160binaries.</p>
Chia-I Wuada46052010-01-21 15:29:14 +0800161
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200162</dd>
Chia-I Wuada46052010-01-21 15:29:14 +0800163
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200164<dt><code>EGL_PLATFORM</code></dt>
165<dd>
Chia-I Wuada46052010-01-21 15:29:14 +0800166
Chia-I Wub365b152010-07-03 17:18:40 +0800167<p>This variable specifies the native platform. The valid values are the same
168as those for <code>--with-egl-platforms</code>. When the variable is not set,
169the main library uses the first platform listed in
Chia-I Wu3418f742010-11-02 23:55:56 +0800170<code>--with-egl-platforms</code> as the native platform.</p>
171
172<p>Extensions like <code>EGL_MESA_drm_display</code> define new functions to
173create displays for non-native platforms. These extensions are usually used by
174applications that support non-native platforms. Setting this variable is
175probably required only for some of the demos found in mesa/demo repository.</p>
Chia-I Wuada46052010-01-21 15:29:14 +0800176
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200177</dd>
Chia-I Wuada46052010-01-21 15:29:14 +0800178
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200179<dt><code>EGL_LOG_LEVEL</code></dt>
180<dd>
Chia-I Wuada46052010-01-21 15:29:14 +0800181
182<p>This changes the log level of the main library and the drivers. The valid
183values are: <code>debug</code>, <code>info</code>, <code>warning</code>, and
184<code>fatal</code>.</p>
185
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200186</dd>
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200187</dl>
Chia-I Wuada46052010-01-21 15:29:14 +0800188
189<h2>EGL Drivers</h2>
190
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200191<dl>
192<dt><code>egl_dri2</code></dt>
193<dd>
Chia-I Wu3418f742010-11-02 23:55:56 +0800194
195<p>This driver supports both <code>x11</code> and <code>drm</code> platforms.
Chia-I Wu65e8f812010-12-25 02:45:13 +0800196It functions as a DRI driver loader. For <code>x11</code> support, it talks to
197the X server directly using (XCB-)DRI2 protocol.</p>
198
199<p>This driver can share DRI drivers with <code>libGL</code>.</p>
Chia-I Wu3418f742010-11-02 23:55:56 +0800200
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200201</dd>
Chia-I Wu3418f742010-11-02 23:55:56 +0800202
Chia-I Wu65e8f812010-12-25 02:45:13 +0800203<h2>Packaging</h2>
204
205<p>The ABI between the main library and its drivers are not stable. Nor is
Jose Fonseca5564c362015-03-03 16:01:22 +0000206there a plan to stabilize it at the moment.</p>
Chia-I Wu65e8f812010-12-25 02:45:13 +0800207
Chia-I Wuada46052010-01-21 15:29:14 +0800208<h2>Developers</h2>
209
Jose Fonseca5564c362015-03-03 16:01:22 +0000210<p>The sources of the main library and drivers can be found at
211<code>src/egl/</code>.</p>
Chia-I Wu14cbf322010-01-27 23:18:22 +0800212
Chia-I Wu14cbf322010-01-27 23:18:22 +0800213<h3>Lifetime of Display Resources</h3>
214
215<p>Contexts and surfaces are examples of display resources. They might live
216longer than the display that creates them.</p>
217
218<p>In EGL, when a display is terminated through <code>eglTerminate</code>, all
219display resources should be destroyed. Similarly, when a thread is released
Nathan Kidd0691b372014-01-03 16:44:00 -0700220through <code>eglReleaseThread</code>, all current display resources should be
221released. Another way to destroy or release resources is through functions
Chia-I Wu14cbf322010-01-27 23:18:22 +0800222such as <code>eglDestroySurface</code> or <code>eglMakeCurrent</code>.</p>
223
224<p>When a resource that is current to some thread is destroyed, the resource
225should not be destroyed immediately. EGL requires the resource to live until
226it is no longer current. A driver usually calls
227<code>eglIs&lt;Resource&gt;Bound</code> to check if a resource is bound
228(current) to any thread in the destroy callbacks. If it is still bound, the
229resource is not destroyed.</p>
230
231<p>The main library will mark destroyed current resources as unlinked. In a
232driver's <code>MakeCurrent</code> callback,
233<code>eglIs&lt;Resource&gt;Linked</code> can then be called to check if a newly
234released resource is linked to a display. If it is not, the last reference to
235the resource is removed and the driver should destroy the resource. But it
236should be careful here because <code>MakeCurrent</code> might be called with an
237uninitialized display.</p>
238
239<p>This is the only mechanism provided by the main library to help manage the
240resources. The drivers are responsible to the correct behavior as defined by
241EGL.</p>
Chia-I Wuada46052010-01-21 15:29:14 +0800242
Chia-I Wu1b2b08c2010-02-05 12:44:45 +0800243<h3><code>EGL_RENDER_BUFFER</code></h3>
244
245<p>In EGL, the color buffer a context should try to render to is decided by the
246binding surface. It should try to render to the front buffer if the binding
247surface has <code>EGL_RENDER_BUFFER</code> set to
248<code>EGL_SINGLE_BUFFER</code>; If the same context is later bound to a
249surface with <code>EGL_RENDER_BUFFER</code> set to
250<code>EGL_BACK_BUFFER</code>, the context should try to render to the back
251buffer. However, the context is allowed to make the final decision as to which
252color buffer it wants to or is able to render to.</p>
253
254<p>For pbuffer surfaces, the render buffer is always
255<code>EGL_BACK_BUFFER</code>. And for pixmap surfaces, the render buffer is
256always <code>EGL_SINGLE_BUFFER</code>. Unlike window surfaces, EGL spec
257requires their <code>EGL_RENDER_BUFFER</code> values to be honored. As a
258result, a driver should never set <code>EGL_PIXMAP_BIT</code> or
259<code>EGL_PBUFFER_BIT</code> bits of a config if the contexts created with the
260config won't be able to honor the <code>EGL_RENDER_BUFFER</code> of pixmap or
261pbuffer surfaces.</p>
262
263<p>It should also be noted that pixmap and pbuffer surfaces are assumed to be
264single-buffered, in that <code>eglSwapBuffers</code> has no effect on them. It
265is desirable that a driver allocates a private color buffer for each pbuffer
266surface created. If the window system the driver supports has native pbuffers,
267or if the native pixmaps have more than one color buffers, the driver should
268carefully attach the native color buffers to the EGL surfaces, re-route them if
269required.</p>
270
271<p>There is no defined behavior as to, for example, how
272<code>glDrawBuffer</code> interacts with <code>EGL_RENDER_BUFFER</code>. Right
273now, it is desired that the draw buffer in a client API be fixed for pixmap and
274pbuffer surfaces. Therefore, the driver is responsible to guarantee that the
275client API renders to the specified render buffer for pixmap and pbuffer
276surfaces.</p>
277
Chia-I Wue16f5772010-02-17 19:52:29 +0800278<h3><code>EGLDisplay</code> Mutex</h3>
279
280The <code>EGLDisplay</code> will be locked before calling any of the dispatch
281functions (well, except for GetProcAddress which does not take an
282<code>EGLDisplay</code>). This guarantees that the same dispatch function will
283not be called with the sample display at the same time. If a driver has access
284to an <code>EGLDisplay</code> without going through the EGL APIs, the driver
285should as well lock the display before using it.
286
Andreas Bollb5da52a2012-09-18 18:57:02 +0200287</div>
Chia-I Wuada46052010-01-21 15:29:14 +0800288</body>
289</html>