diff options
| author | Laura Ekstrand <laura@jlekstrand.net> | 2018-04-02 20:42:15 -0700 |
|---|---|---|
| committer | Laura Ekstrand <laura@jlekstrand.net> | 2018-04-02 20:42:15 -0700 |
| commit | 8d1cf0cdecf9300e36e78a2120ab95898a767ac5 (patch) | |
| tree | 1c174515fd73c0cef591299ee7fd35eacb9e07c8 | |
| parent | 9177fd4597a92e6d5d6121291638e95d99e87c78 (diff) | |
Parse devinfo.rst to RST.
| -rw-r--r-- | docs/devinfo.rst | 98 |
1 files changed, 30 insertions, 68 deletions
diff --git a/docs/devinfo.rst b/docs/devinfo.rst index c6e97c68a6..2fe60fcd13 100644 --- a/docs/devinfo.rst +++ b/docs/devinfo.rst @@ -1,83 +1,45 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> -<html lang="en"> -<head> - <meta http-equiv="content-type" content="text/html; charset=utf-8"> - <title>Development Notes</title> - <link rel="stylesheet" type="text/css" href="mesa.css"> -</head> -<body> +Development Notes +================= -<div class="header"> - <h1>The Mesa 3D Graphics Library</h1> -</div> - -<iframe src="contents.html"></iframe> -<div class="content"> - -<h1>Development Notes</h1> +Adding Extensions +----------------- +To add a new GL extension to Mesa you have to do at least the following. -<ul> -<li><a href="#extensions">Adding Extensions</a> -</ul> +- If glext.h doesn't define the extension, edit include/GL/gl.h and add + code like this: -<h2 id="extensions">Adding Extensions</h2> + .. code-block:: c -<p> -To add a new GL extension to Mesa you have to do at least the following. + #ifndef GL_EXT_the_extension_name + #define GL_EXT_the_extension_name 1 + /* declare the new enum tokens */ + /* prototype the new functions */ + /* TYPEDEFS for the new functions */ + #endif -<ul> -<li> - If glext.h doesn't define the extension, edit include/GL/gl.h and add - code like this: - <pre> - #ifndef GL_EXT_the_extension_name - #define GL_EXT_the_extension_name 1 - /* declare the new enum tokens */ - /* prototype the new functions */ - /* TYPEDEFS for the new functions */ - #endif - </pre> -</li> -<li> - In the src/mapi/glapi/gen/ directory, add the new extension functions and - enums to the gl_API.xml file. +- In the src/mapi/glapi/gen/ directory, add the new extension functions and + enums to the gl\_API.xml file. Then, a bunch of source files must be regenerated by executing the corresponding Python scripts. -</li> -<li> - Add a new entry to the <code>gl_extensions</code> struct in mtypes.h + +- Add a new entry to the ``gl_extensions`` struct in mtypes.h if the extension requires driver capabilities not already exposed by another extension. -</li> -<li> - Add a new entry to the src/mesa/main/extensions_table.h file. -</li> -<li> - From this point, the best way to proceed is to find another extension, + +- Add a new entry to the src/mesa/main/extensions\_table.h file. + +- From this point, the best way to proceed is to find another extension, similar to the new one, that's already implemented in Mesa and use it as an example. -</li> -<li> - If the new extension adds new GL state, the functions in get.c, enable.c - and attrib.c will most likely require new code. -</li> -<li> - To determine if the new extension is active in the current context, - use the auto-generated _mesa_has_##name_str() function defined in - src/mesa/main/extensions.h. -</li> -<li> - The dispatch tests check_table.cpp and dispatch_sanity.cpp - should be updated with details about the new extensions functions. These - tests are run using 'make check' -</li> -</ul> -</p> - +- If the new extension adds new GL state, the functions in get.c, enable.c + and attrib.c will most likely require new code. +- To determine if the new extension is active in the current context, + use the auto-generated ``_mesa_has_##name_str()`` function defined in + src/mesa/main/extensions.h. -</div> -</body> -</html> +- The dispatch tests check\_table.cpp and dispatch\_sanity.cpp + should be updated with details about the new extensions functions. These + tests are run using ``make check`` |