<TITLE>Development Notes</TITLE>
-<BODY text="#000000" bgcolor="#55bbff" link="#111188">
+<link rel="stylesheet" type="text/css" href="mesa.css"></head>
+
+<BODY>
<H1>Development Notes</H1>
<H2>Adding Extentions</H2>
<p>
-To add a new GL extension to Mesa you have to do the following.
-<pre>
- If glext.h doesn't define the extension, edit include/GL/gl.h and add:
- - new enum tokens
- - new API function entry points
- - #define GL_EXT_the_extension_name 1
-
- If adding a new API function (call it glNewFunctionEXT):
- - insert glNewFunctionEXT()into src/apiext.h
- - edit src/types.h and add NewFunction to the gl_api_table struct
- - implement gl_NewFunction() in the appropriate src file
- - hook gl_NewFunction() into pointers.c
- - add display list support in dlist.c for save_NewFunction()
- - add glNewFunctionEXT to gl_GetProcAddress() in extensions.c or
- in the device driver's GetProcAddress() function if appropriate
-</pre>
-<p>
-If adding new GL state be sure to update get.c and enable.c
-</p>
-<p>
-In general, look for an extension similar to the new one that's already
-implemented in Mesa and follow it by example.
-</p>
+To add a new GL extension to Mesa you have to do at least the following.
+
+<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/mesa/glapi/ 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
+</li>
+<li>
+ Update the <code>extensions.c</code> file.
+</li>
+<li>
+ 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>
+</ul>
Here's the GNU indent command which will best approximate my preferred style:
</p>
<pre>
- indent -br -i3 -npcs infile.c -o outfile.c
+ indent -br -i3 -npcs --no-tabs infile.c -o outfile.c
</pre>
</p>
<p>
-Global vars not allowed.
+Global variables are not allowed.
</p>
<p>
</pre>
-<H2>Writing a Device Driver</H2>
-
-<p>
-XXX to do
-</p>
-
-
-
<H2>Making a New Mesa Release</H2>
<p>
These are the instructions for making a new Mesa release.
</p>
+<H3>Get latest source files</H3>
<p>
-Prerequisites (later versions may work):
+Use git to get the latest Mesa files from the git repository, from whatever
+branch is relevant.
</p>
-<ul>
-<li> autoconf 2.50
-<li> automake 1.4-p2
-<li> libtool 1.4
-</ul>
-<p>
-Be sure to do a "cvs update -d ." in the Mesa directory to
-get all the latest files.
-</p>
-
-<p>
-Update the version definitions in src/version.h
-</p>
+<H3>Verify and update version info</H3>
<p>
-Create/edit the docs/RELNOTES-X.Y file to document what's new in the release.
-Edit the docs/VERSIONS file too.
+Create/edit the docs/relnotes-x.y.html file to document what's new in the release.
+Add the new relnotes-x.y.html file to <a href="relnotes.html">relnotes.html</a>.
</p>
<p>
-Edit Make-config and change the MESA_MAJOR and/or MESA_MINOR versions.
+Update the MESA_MAJOR, MESA_MINOR and MESA_TINY version numbers in
+configs/default.
+Also update the VERSION line in the top-level Makefile.
</p>
<p>
-Edit the GNU configure stuff to change versions numbers as needed:
-Update the version string (second argument) in the line
-"AM_INIT_AUTOMAKE(Mesa, 3.3)" in the configure.in file.
+Make sure the values in src/mesa/main/version.h are correct.
</p>
<p>
-Remove the leading `dnl' from the line "dnl AM_MAINTAINER_MODE".
+Update the docs/news.html file and docs/download.html files.
</p>
<p>
-Verify the version numbers near the top of configure.in
+Check in all updates to git.
</p>
<p>
-Run "fixam -f" to disable automatic dependency tracking.
+Tag the files with the release name (in the form <b>mesa_X_Y</b>)
+with: <code>git tag -a mesa_X_Y</code>
+Then: <code>git push origin mesa_X_Y</code>
</p>
-<p>
-Run the bootstrap script to generate the configure script.
-</p>
+<H3>Make the tarballs</H3>
<p>
-Edit Makefile.X11 and verify DIRECTORY is set correctly. The Mesa
-sources must be in that directory (or there must be a symbolic link).
+Make a symbolic link from $(DIRECTORY) to 'Mesa'. For example,
+<code>ln -s Mesa Mesa-7.5</code>
+This is needed in order to make a correct tar file in the next step.
</p>
<p>
-Edit Makefile.X11 and verify that LIB_NAME and DEMO_NAME are correct.
-If it's a beta release, be sure the bump up the beta release number.
-</p>
+Make the distribution files. From inside the Mesa directory:
+<pre>
+ make tarballs
+</pre>
<p>
-cp Makefile.X11 to Makefile so that the old-style Mesa makefiles
-still work. ./configure will overwrite it if that's what the user runs.
+After the tarballs are created, the md5 checksums for the files will
+be computed.
+Add them to the docs/relnotes-X.Y.html file.
</p>
<p>
-Make a symbolic link from $(DIRECTORY) to Mesa. For example,
-ln -s Mesa Mesa-3.3 This is needed in order to make a correct
-tar file in the next step.
+Copy the distribution files to a temporary directory, unpack them,
+compile everything, and run some demos to be sure everything works.
</p>
+<H3>Update the website and announce the release</H3>
<p>
-Make the distribution files. From inside the Mesa directory:
-<pre>
- make -f Makefile.X11 lib_tar
- make -f Makefile.X11 demo_tar
- make -f Makefile.X11 lib_zip
- make -f Makefile.X11 demo_zip
-</pre>
-
-<p>
-Copy the distribution files to a temporary directory, unpack them,
-compile everything, and run some demos to be sure everything works.
+Follow the directions on SourceForge for creating a new "release" and
+uploading the tarballs.
</p>
<p>
-Upload the *.tar.gz and *.zip files to ftp.mesa3d.org
+Basically, to upload the tarball files with:
+<br>
+<code>
+rsync -avP ssh Mesa*-X.Y.* USERNAME@frs.sourceforge.net:uploads/
+</code>
</p>
<p>
-Update the web site.
+Update the web site by copying the docs/ directory's files to
+/home/users/b/br/brianp/mesa-www/htdocs/ with:
+<br>
+<code>
+sftp USERNAME,mesa3d@web.sourceforge.net
+</code>
</p>
<p>
</p>
-<H2>Autoconf info</H2>
-
-<p>
-In order to run the bootstrap script you'll need:
-<p>
-<pre>
-autoconf 2.50
-automake 1.4-p5
-libtool 1.4
-</pre>
-
</body>
</html>