head 1.2;
access;
symbols
netbsd-8-3-RELEASE:1.1.1.5
netbsd-9-4-RELEASE:1.1.1.6
netbsd-9-3-RELEASE:1.1.1.6
netbsd-9-2-RELEASE:1.1.1.6
netbsd-9-1-RELEASE:1.1.1.6
netbsd-8-2-RELEASE:1.1.1.5
netbsd-9-0-RELEASE:1.1.1.6
netbsd-9-0-RC2:1.1.1.6
netbsd-9-0-RC1:1.1.1.6
mesalib-19-1-7:1.1.1.7
netbsd-9:1.1.1.6.0.2
netbsd-9-base:1.1.1.6
mesa-18-3-6:1.1.1.6
netbsd-8-1-RELEASE:1.1.1.5
netbsd-8-1-RC1:1.1.1.5
mesa-18-3-4:1.1.1.6
netbsd-7-2-RELEASE:1.1.1.4.10.1
netbsd-8-0-RELEASE:1.1.1.5
netbsd-8-0-RC2:1.1.1.5
netbsd-8-0-RC1:1.1.1.5
netbsd-7-1-2-RELEASE:1.1.1.4.10.1
netbsd-7-1-1-RELEASE:1.1.1.4.10.1
netbsd-8:1.1.1.5.0.2
netbsd-8-base:1.1.1.5
netbsd-7-1:1.1.1.4.10.1.0.4
netbsd-7-1-RELEASE:1.1.1.4.10.1
netbsd-7-1-RC2:1.1.1.4.10.1
netbsd-7-1-RC1:1.1.1.4.10.1
netbsd-7-0-2-RELEASE:1.1.1.4.10.1
netbsd-7-0-1-RELEASE:1.1.1.4.10.1
netbsd-7-0:1.1.1.4.10.1.0.2
netbsd-7-0-RELEASE:1.1.1.4.10.1
netbsd-7-0-RC3:1.1.1.4.10.1
netbsd-7-0-RC2:1.1.1.4.10.1
netbsd-7-0-RC1:1.1.1.4.10.1
MesaLib-10-3-5:1.1.1.5
netbsd-5-2-3-RELEASE:1.1.1.1.2.1
netbsd-5-1-5-RELEASE:1.1.1.1.2.1
netbsd-6-0-6-RELEASE:1.1.1.4
netbsd-6-1-5-RELEASE:1.1.1.4
netbsd-7:1.1.1.4.0.10
netbsd-7-base:1.1.1.4
MesaLib-7-11-2:1.1.1.4
netbsd-6-1-4-RELEASE:1.1.1.4
netbsd-6-0-5-RELEASE:1.1.1.4
riastradh-xf86-video-intel-2-7-1-pre-2-21-15:1.1.1.4
riastradh-drm2:1.1.1.4.0.8
riastradh-drm2-base:1.1.1.4
netbsd-6-1-3-RELEASE:1.1.1.4
netbsd-6-0-4-RELEASE:1.1.1.4
netbsd-5-2-2-RELEASE:1.1.1.1.2.1
netbsd-5-1-4-RELEASE:1.1.1.1.2.1
netbsd-6-1-2-RELEASE:1.1.1.4
netbsd-6-0-3-RELEASE:1.1.1.4
netbsd-5-2-1-RELEASE:1.1.1.1.2.1
netbsd-5-1-3-RELEASE:1.1.1.1.2.1
netbsd-6-1-1-RELEASE:1.1.1.4
netbsd-6-1:1.1.1.4.0.6
netbsd-6-0-2-RELEASE:1.1.1.4
netbsd-6-1-RELEASE:1.1.1.4
netbsd-6-1-RC4:1.1.1.4
netbsd-6-1-RC3:1.1.1.4
netbsd-6-1-RC2:1.1.1.4
netbsd-6-1-RC1:1.1.1.4
netbsd-5-2:1.1.1.1.2.1.0.4
netbsd-6-0-1-RELEASE:1.1.1.4
netbsd-5-2-RELEASE:1.1.1.1.2.1
netbsd-5-2-RC1:1.1.1.1.2.1
netbsd-6-0:1.1.1.4.0.4
netbsd-6-0-RELEASE:1.1.1.4
netbsd-6-0-RC2:1.1.1.4
netbsd-6-0-RC1:1.1.1.4
netbsd-6:1.1.1.4.0.2
netbsd-6-base:1.1.1.4
netbsd-5-1-2-RELEASE:1.1.1.1.2.1
netbsd-5-1-1-RELEASE:1.1.1.1.2.1
netbsd-5-1:1.1.1.1.2.1.0.2
netbsd-5-1-RELEASE:1.1.1.1.2.1
netbsd-5-1-RC4:1.1.1.1.2.1
MesaLib-7-8-2:1.1.1.4
netbsd-5-1-RC3:1.1.1.1.2.1
MesaLib-7-7-1:1.1.1.3
netbsd-5-1-RC2:1.1.1.1.2.1
netbsd-5-1-RC1:1.1.1.1.2.1
netbsd-5-0-2-RELEASE:1.1.1.1
MesaLib-7-4-4:1.1.1.2
netbsd-5-0-1-RELEASE:1.1.1.1
MesaLib-7-4-2:1.1.1.2
netbsd-5-0:1.1.1.1.0.4
netbsd-5-0-RELEASE:1.1.1.1
netbsd-5-0-RC4:1.1.1.1
netbsd-5-0-RC3:1.1.1.1
netbsd-5-0-RC2:1.1.1.1
netbsd-5-0-RC1:1.1.1.1
netbsd-5:1.1.1.1.0.2
netbsd-5-base:1.1.1.1
MesaLib-7-0-3:1.1.1.1
xorg:1.1.1;
locks; strict;
comment @# @;
1.2
date 2022.05.09.01.27.12; author mrg; state dead;
branches;
next 1.1;
commitid vdvqJ71xlVGCRjDD;
1.1
date 2008.07.29.05.08.16; author mrg; state Exp;
branches
1.1.1.1;
next ;
1.1.1.1
date 2008.07.29.05.08.16; author mrg; state Exp;
branches
1.1.1.1.2.1;
next 1.1.1.2;
1.1.1.2
date 2009.06.11.00.50.15; author mrg; state Exp;
branches;
next 1.1.1.3;
1.1.1.3
date 2010.05.23.21.22.15; author mrg; state Exp;
branches;
next 1.1.1.4;
1.1.1.4
date 2010.07.19.05.31.51; author mrg; state Exp;
branches
1.1.1.4.10.1;
next 1.1.1.5;
1.1.1.5
date 2014.12.18.06.02.09; author mrg; state Exp;
branches;
next 1.1.1.6;
commitid tzEjkwzaREfP8u2y;
1.1.1.6
date 2019.03.10.03.42.48; author mrg; state Exp;
branches;
next 1.1.1.7;
commitid r12jo1Nf3ebQKLeB;
1.1.1.7
date 2019.09.24.16.19.30; author maya; state Exp;
branches;
next ;
commitid KJXusGl8fi9AAhEB;
1.1.1.1.2.1
date 2009.09.17.03.32.04; author snj; state Exp;
branches;
next ;
1.1.1.4.10.1
date 2015.01.05.20.58.24; author martin; state Exp;
branches;
next ;
commitid 1yEFPaBBlEWKuS4y;
desc
@@
1.2
log
@merge mesa 21.3.7.
@
text
@
Development Notes
Development Notes
Adding Extentions
To add a new GL extension to Mesa you have to do at least the following.
If glext.h doesn't define the extension, edit include/GL/gl.h and add
code like this:
#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
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.
Add a new entry to the gl_extensions struct in mtypes.h
Update the extensions.c 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.
If the new extension adds new GL state, the functions in get.c, enable.c
and attrib.c will most likely require new code.
Coding Style
Mesa's code style has changed over the years. Here's the latest.
Comment your code! It's extremely important that open-source code be
well documented. Also, strive to write clean, easily understandable code.
3-space indentation
If you use tabs, set them to 8 columns
Brace example:
if (condition) {
foo;
}
else {
bar;
}
Here's the GNU indent command which will best approximate my preferred style:
Local variable name example: localVarName (no underscores)
Constants and macros are ALL_UPPERCASE, with _ between words
Global variables are not allowed.
Function name examples:
glFooBar() - a public GL entry point (in dispatch.c)
_mesa_FooBar() - the internal immediate mode function
save_FooBar() - retained mode (display list) function in dlist.c
foo_bar() - a static (private) function
_mesa_foo_bar() - an internal non-static Mesa function
Making a New Mesa Release
These are the instructions for making a new Mesa release.
Get latest source files
Use "cvs update -dAP " to get the latest Mesa files from CVS.
Verify and update version info
Create/edit the docs/RELNOTES-X.Y file to document what's new in the release.
Add the new RELNOTES-X.Y file to relnotes.html.
Update the docs/VERSIONS file too.
Edit configs/default and change the MESA_MAJOR, MESA_MINOR and MESA_TINY
version numbers.
Make sure the values in src/mesa/main/version.h is correct.
Edit the top-level Makefile and verify that DIRECTORY, LIB_NAME and
DEMO_NAME are correct.
Update the docs/news.html file and docs/download.html files.
Check in all updates to CVS.
Tag the CVS files with the release name (in the form mesa_X_Y).
Make the tarballs
Make a symbolic link from $(DIRECTORY) to 'Mesa'. For example,
ln -s Mesa Mesa-6.3
This is needed in order to make a correct tar file in the next step.
Make the distribution files. From inside the Mesa directory:
make tarballs
After the tarballs are created, the md5 checksums for the files will
be computed.
Add them to the docs/news.html file.
Copy the distribution files to a temporary directory, unpack them,
compile everything, and run some demos to be sure everything works.
Update the website and announce the release
Follow the directions on SourceForge for creating a new "release" and
uploading the tarballs.
Update the web site by copying the docs/ directory's files to
/home/users/b/br/brianp/mesa-www/htdocs/
Make an announcement on the mailing lists:
mesa3d-dev@@lists.sf.net,
mesa3d-users@@lists.sf.net
and
mesa3d-announce@@lists.sf.net