blob: 2bc8f2372728822c69d6275ef71559b949b6df0e [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
Eric Engestrom30cf9ff2017-02-09 02:10:17 +000021<a href="https://www.khronos.org/egl/">
22https://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
Eric Engestrom077879c2017-02-26 23:58:03 +000047options enables the listed classic 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
Emil Velikov73682f82016-11-25 18:34:03 +000080<dt><code>--with-platforms</code></dt>
Andreas Boll76d4f9e2012-09-20 16:01:08 +020081<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
Emil Velikov73682f82016-11-25 18:34:03 +000084separated string such as <code>--with-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
Emil Velikov73682f82016-11-25 18:34:03 +000086the main library to decide the native platform.</p>
Chia-I Wuada46052010-01-21 15:29:14 +080087
Chia-I Wue7424d72010-09-19 16:54:39 +080088<p>The available platforms are <code>x11</code>, <code>drm</code>,
Emil Velikovb0a92992015-07-10 00:16:21 +010089<code>wayland</code>, <code>surfaceless</code>, <code>android</code>,
Nicolas Boichata9b2b5e2016-05-24 13:55:20 +080090and <code>haiku</code>.
91The <code>android</code> platform can either be built as a system
92component, part of AOSP, using <code>Android.mk</code> files, or
93cross-compiled using appropriate <code>configure</code> options.
94The <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>
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200133<dt><code>EGL_PLATFORM</code></dt>
134<dd>
Chia-I Wuada46052010-01-21 15:29:14 +0800135
Chia-I Wub365b152010-07-03 17:18:40 +0800136<p>This variable specifies the native platform. The valid values are the same
Emil Velikov73682f82016-11-25 18:34:03 +0000137as those for <code>--with-platforms</code>. When the variable is not set,
Chia-I Wub365b152010-07-03 17:18:40 +0800138the main library uses the first platform listed in
Emil Velikov73682f82016-11-25 18:34:03 +0000139<code>--with-platforms</code> as the native platform.</p>
Chia-I Wu3418f742010-11-02 23:55:56 +0800140
141<p>Extensions like <code>EGL_MESA_drm_display</code> define new functions to
142create displays for non-native platforms. These extensions are usually used by
143applications that support non-native platforms. Setting this variable is
144probably required only for some of the demos found in mesa/demo repository.</p>
Chia-I Wuada46052010-01-21 15:29:14 +0800145
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200146</dd>
Chia-I Wuada46052010-01-21 15:29:14 +0800147
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200148<dt><code>EGL_LOG_LEVEL</code></dt>
149<dd>
Chia-I Wuada46052010-01-21 15:29:14 +0800150
151<p>This changes the log level of the main library and the drivers. The valid
152values are: <code>debug</code>, <code>info</code>, <code>warning</code>, and
153<code>fatal</code>.</p>
154
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200155</dd>
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200156</dl>
Chia-I Wuada46052010-01-21 15:29:14 +0800157
158<h2>EGL Drivers</h2>
159
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200160<dl>
161<dt><code>egl_dri2</code></dt>
162<dd>
Chia-I Wu3418f742010-11-02 23:55:56 +0800163
164<p>This driver supports both <code>x11</code> and <code>drm</code> platforms.
Chia-I Wu65e8f812010-12-25 02:45:13 +0800165It functions as a DRI driver loader. For <code>x11</code> support, it talks to
166the X server directly using (XCB-)DRI2 protocol.</p>
167
168<p>This driver can share DRI drivers with <code>libGL</code>.</p>
Chia-I Wu3418f742010-11-02 23:55:56 +0800169
Andreas Boll76d4f9e2012-09-20 16:01:08 +0200170</dd>
Eric Engestrom09a6cb72018-05-23 12:46:44 +0100171</dl>
Chia-I Wu3418f742010-11-02 23:55:56 +0800172
Chia-I Wu65e8f812010-12-25 02:45:13 +0800173<h2>Packaging</h2>
174
175<p>The ABI between the main library and its drivers are not stable. Nor is
Jose Fonseca5564c362015-03-03 16:01:22 +0000176there a plan to stabilize it at the moment.</p>
Chia-I Wu65e8f812010-12-25 02:45:13 +0800177
Chia-I Wuada46052010-01-21 15:29:14 +0800178<h2>Developers</h2>
179
Jose Fonseca5564c362015-03-03 16:01:22 +0000180<p>The sources of the main library and drivers can be found at
181<code>src/egl/</code>.</p>
Chia-I Wu14cbf322010-01-27 23:18:22 +0800182
Chia-I Wu14cbf322010-01-27 23:18:22 +0800183<h3>Lifetime of Display Resources</h3>
184
185<p>Contexts and surfaces are examples of display resources. They might live
186longer than the display that creates them.</p>
187
188<p>In EGL, when a display is terminated through <code>eglTerminate</code>, all
189display resources should be destroyed. Similarly, when a thread is released
Nathan Kidd0691b372014-01-03 16:44:00 -0700190through <code>eglReleaseThread</code>, all current display resources should be
191released. Another way to destroy or release resources is through functions
Chia-I Wu14cbf322010-01-27 23:18:22 +0800192such as <code>eglDestroySurface</code> or <code>eglMakeCurrent</code>.</p>
193
194<p>When a resource that is current to some thread is destroyed, the resource
195should not be destroyed immediately. EGL requires the resource to live until
196it is no longer current. A driver usually calls
197<code>eglIs&lt;Resource&gt;Bound</code> to check if a resource is bound
198(current) to any thread in the destroy callbacks. If it is still bound, the
199resource is not destroyed.</p>
200
201<p>The main library will mark destroyed current resources as unlinked. In a
202driver's <code>MakeCurrent</code> callback,
203<code>eglIs&lt;Resource&gt;Linked</code> can then be called to check if a newly
204released resource is linked to a display. If it is not, the last reference to
205the resource is removed and the driver should destroy the resource. But it
206should be careful here because <code>MakeCurrent</code> might be called with an
207uninitialized display.</p>
208
209<p>This is the only mechanism provided by the main library to help manage the
210resources. The drivers are responsible to the correct behavior as defined by
211EGL.</p>
Chia-I Wuada46052010-01-21 15:29:14 +0800212
Chia-I Wu1b2b08c2010-02-05 12:44:45 +0800213<h3><code>EGL_RENDER_BUFFER</code></h3>
214
215<p>In EGL, the color buffer a context should try to render to is decided by the
216binding surface. It should try to render to the front buffer if the binding
217surface has <code>EGL_RENDER_BUFFER</code> set to
218<code>EGL_SINGLE_BUFFER</code>; If the same context is later bound to a
219surface with <code>EGL_RENDER_BUFFER</code> set to
220<code>EGL_BACK_BUFFER</code>, the context should try to render to the back
221buffer. However, the context is allowed to make the final decision as to which
222color buffer it wants to or is able to render to.</p>
223
224<p>For pbuffer surfaces, the render buffer is always
225<code>EGL_BACK_BUFFER</code>. And for pixmap surfaces, the render buffer is
226always <code>EGL_SINGLE_BUFFER</code>. Unlike window surfaces, EGL spec
227requires their <code>EGL_RENDER_BUFFER</code> values to be honored. As a
228result, a driver should never set <code>EGL_PIXMAP_BIT</code> or
229<code>EGL_PBUFFER_BIT</code> bits of a config if the contexts created with the
230config won't be able to honor the <code>EGL_RENDER_BUFFER</code> of pixmap or
231pbuffer surfaces.</p>
232
233<p>It should also be noted that pixmap and pbuffer surfaces are assumed to be
234single-buffered, in that <code>eglSwapBuffers</code> has no effect on them. It
235is desirable that a driver allocates a private color buffer for each pbuffer
236surface created. If the window system the driver supports has native pbuffers,
237or if the native pixmaps have more than one color buffers, the driver should
238carefully attach the native color buffers to the EGL surfaces, re-route them if
239required.</p>
240
241<p>There is no defined behavior as to, for example, how
242<code>glDrawBuffer</code> interacts with <code>EGL_RENDER_BUFFER</code>. Right
243now, it is desired that the draw buffer in a client API be fixed for pixmap and
244pbuffer surfaces. Therefore, the driver is responsible to guarantee that the
245client API renders to the specified render buffer for pixmap and pbuffer
246surfaces.</p>
247
Chia-I Wue16f5772010-02-17 19:52:29 +0800248<h3><code>EGLDisplay</code> Mutex</h3>
249
250The <code>EGLDisplay</code> will be locked before calling any of the dispatch
251functions (well, except for GetProcAddress which does not take an
252<code>EGLDisplay</code>). This guarantees that the same dispatch function will
253not be called with the sample display at the same time. If a driver has access
254to an <code>EGLDisplay</code> without going through the EGL APIs, the driver
255should as well lock the display before using it.
256
Andreas Bollb5da52a2012-09-18 18:57:02 +0200257</div>
Chia-I Wuada46052010-01-21 15:29:14 +0800258</body>
259</html>