X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=docs%2Fdevinfo.html;h=0fb816749ed39b8866072275416cc1f96401a3a5;hb=3be1c11001be872a6850607955e61e82a470c064;hp=c1ddea3e4b955bc65626f6b397e42c1dce0e6cc4;hpb=51830613a941d07e19f38f328657864ca2326111;p=mesa.git diff --git a/docs/devinfo.html b/docs/devinfo.html index c1ddea3e4b9..0fb816749ed 100644 --- a/docs/devinfo.html +++ b/docs/devinfo.html @@ -2,7 +2,9 @@ Development Notes - + + +

Development Notes

@@ -32,14 +34,18 @@ To add a new GL extension to Mesa you have to do at least the following. corresponding Python scripts.

- Find an existing extension that's similar to the new one and search - the sources for code related to that extension. - Implement new code as needed. - In general, new state variables will be added to mtypes.h. If the - extension is rather large, try to implement it in a new source file. + 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 hew extension adds new GL state, the functions in get.c, enable.c + If the new extension adds new GL state, the functions in get.c, enable.c and attrib.c will most likely require new code.

@@ -81,7 +87,7 @@ Brace example: Here's the GNU indent command which will best approximate my preferred style:

-	indent -br -i3 -npcs infile.c -o outfile.c
+	indent -br -i3 -npcs --no-tabs infile.c -o outfile.c

@@ -94,7 +100,7 @@ Constants and macros are ALL_UPPERCASE, with _ between words

-Global vars not allowed. +Global variables are not allowed.

@@ -109,110 +115,95 @@ Function name examples: -

Writing a Device Driver

- -

-XXX to do -

- - -

Making a New Mesa Release

These are the instructions for making a new Mesa release.

Get latest source files

-Prerequisites (later versions may work): -

autoconf 2.50 -
automake 1.4-p2 -
libtool 1.4 -

- -

-Be sure to do a "cvs update -d ." in the Mesa directory to -get all the latest files. +Use git to get the latest Mesa files from the git repository, from whatever +branch is relevant.

-Update the version definitions in src/version.h -

Verify and update version info

-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 relnotes.html.

-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.

-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.

-Remove the leading `dnl' from the line "dnl AM_MAINTAINER_MODE". +Update the docs/news.html file and docs/download.html files.

-Verify the version numbers near the top of configure.in +Check in all updates to git.

-Run "fixam -f" to disable automatic dependency tracking. +Tag the files with the release name (in the form mesa_X_Y) +with: git tag -a mesa_X_Y +Then: git push origin mesa_X_Y

-Run the bootstrap script to generate the configure script. -

Make the tarballs

-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, +ln -s Mesa Mesa-7.5 +This is needed in order to make a correct tar file in the next step.

-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. -

+Make the distribution files. From inside the Mesa directory: +

+	make tarballs
+

-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.

-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.

Update the website and announce the release

-Make the distribution files. From inside the Mesa directory: -

-	make -f Makefile.X11 lib_tar
-	make -f Makefile.X11 demo_tar
-	make -f Makefile.X11 lib_zip
-	make -f Makefile.X11 demo_zip
-

- -

-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.

-Upload the *.tar.gz and *.zip files to ftp.mesa3d.org +Basically, to upload the tarball files with: +
++rsync -avP ssh Mesa*-X.Y.* USERNAME@frs.sourceforge.net:uploads/ +

-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: +
++sftp USERNAME,mesa3d@web.sourceforge.net +

@@ -224,17 +215,6 @@ and

Autoconf info

- -

-In order to run the bootstrap script you'll need: -

-autoconf 2.50
-automake 1.4-p5
-libtool 1.4
-