X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=docs%2Fdevinfo.html;h=cce14d73a365e40627e2966c1ca8fa063e6f0268;hb=9d43e387a3391b091f0a22710a7414a52eafae33;hp=e1761be22340ebcea62deb3ef2e2268a7399133c;hpb=9cef3efc299b7cafb5720782fc1ed5731f47d7ce;p=mesa.git diff --git a/docs/devinfo.html b/docs/devinfo.html index e1761be2234..cce14d73a36 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,31 +115,22 @@ 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

    -Be sure to do a "cvs update -d ." in the Mesa directory to -get all the latest files. +Use "cvs update -dAP " to get the latest Mesa files from CVS.

    -

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

    +

    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.

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

    @@ -159,17 +174,26 @@ 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

    -Upload the *.tar.gz and *.zip files to ftp.mesa3d.org +Follow the directions on SourceForge for creating a new "release" and +uploading the tarballs.

    -Update the web site. +Update the web site by copying the docs/ directory's files to +/home/users/b/br/brianp/mesa-www/htdocs/