From 2ce12f084113a0097fa1a0d67e2f8fe1ab70092b Mon Sep 17 00:00:00 2001 From: marha Date: Fri, 15 Jul 2011 11:25:17 +0200 Subject: xserver libX11 mesa git update 15 July --- mesalib/docs/autoconf.html | 8 - mesalib/docs/devinfo.html | 436 +++++++++++++++++++++---------------------- mesalib/docs/download.html | 5 +- mesalib/docs/faq.html | 6 +- mesalib/docs/license.html | 8 +- mesalib/docs/sourcetree.html | 331 ++++++++++++++++---------------- 6 files changed, 389 insertions(+), 405 deletions(-) (limited to 'mesalib/docs') diff --git a/mesalib/docs/autoconf.html b/mesalib/docs/autoconf.html index 936ddcffe..64bcbd48a 100644 --- a/mesalib/docs/autoconf.html +++ b/mesalib/docs/autoconf.html @@ -21,7 +21,6 @@
  • Demo Program Options
    • @@ -252,13 +251,6 @@ on all drivers. This can be disable with the option if libGLU has been enabled. This can be disable with the option --disable-glw. - - -
  • GLUT - The libglut library will be built by default -if libGLU has been enabled and the glut source code from the MesaGLUT -tarball is available. This can be disable with the option ---disable-glut. -

    • diff --git a/mesalib/docs/devinfo.html b/mesalib/docs/devinfo.html index b2cbf17b4..8887dd026 100644 --- a/mesalib/docs/devinfo.html +++ b/mesalib/docs/devinfo.html @@ -1,221 +1,215 @@ - - -Development Notes - - - - - -

    Development Notes

    - - -

    Adding Extentions

    - -

    -To add a new GL extension to Mesa you have to do at least the following. - -

    - - - -

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

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

    -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 glapi_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 git to get the latest Mesa files from the git repository, from whatever -branch is relevant. -

    - - -

    Verify and update version info

    -

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

    - -

    -Update the MESA_MAJOR, MESA_MINOR and MESA_TINY version numbers in -configs/default. -Also update the VERSION line in the top-level Makefile. -

    - -

    -Make sure the values in src/mesa/main/version.h are correct. -

    - -

    -Update docs/news.html. -

    - -

    -Check in all updates to git. -

    - -

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

    - - -

    Make the tarballs

    -

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

    - -

    -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/relnotes-X.Y.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. -

    - -

    -Basically, to upload the tarball files with: -
    - -rsync -avP ssh Mesa*-X.Y.* USERNAME@frs.sourceforge.net:uploads/ - -

    - -

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

    - -

    -Make an announcement on the mailing lists: - -mesa-dev@lists.freedesktop.org, -mesa-users@lists.freedesktop.org -and -mesa-announce@lists.freedesktop.org -

    - - - - - + + +Development Notes + + + + + +

    Development Notes

    + + +

    Adding Extentions

    + +

    +To add a new GL extension to Mesa you have to do at least the following. + +

    + + + +

    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: +

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

    +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 glapi_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 git to get the latest Mesa files from the git repository, from whatever +branch is relevant. +

    + + +

    Verify and update version info

    +

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

    + +

    +Update the MESA_MAJOR, MESA_MINOR and MESA_TINY version numbers in +configs/default. +Also update the VERSION line in the top-level Makefile. +

    + +

    +Make sure the values in src/mesa/main/version.h are correct. +

    + +

    +Update docs/news.html. +

    + +

    +Check in all updates to git. +

    + +

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

    + + +

    Make the tarballs

    +

    +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/relnotes-X.Y.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. +

    + +

    +Basically, to upload the tarball files with: +
    + +rsync -avP ssh Mesa*-X.Y.* USERNAME@frs.sourceforge.net:uploads/ + +

    + +

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

    + +

    +Make an announcement on the mailing lists: + +mesa-dev@lists.freedesktop.org, +mesa-users@lists.freedesktop.org +and +mesa-announce@lists.freedesktop.org +

    + + + + + diff --git a/mesalib/docs/download.html b/mesalib/docs/download.html index 03fa60b4d..3c4d5976c 100644 --- a/mesalib/docs/download.html +++ b/mesalib/docs/download.html @@ -25,9 +25,8 @@ The Mesa package is named MesaLib-x.y.z.{tar.bz2, tar.gz, zip} where x.y.z is the version. There are three types of compressed archives.

    -There's also the MesaGLUT-x.y.z.{tar.bz2, tar.gz, zip} packages which -contain Mark Kilgard's GLUT library. -This is optional. +In the past, there was also MesaGLUT-x.y.z.{tar.bz2, tar.gz, zip} packages which +contained Mark Kilgard's GLUT library. Most Linux distributions include an implementation of GLUT (such as freeglut).

    diff --git a/mesalib/docs/faq.html b/mesalib/docs/faq.html index 65e279aac..071381c5a 100644 --- a/mesalib/docs/faq.html +++ b/mesalib/docs/faq.html @@ -198,9 +198,9 @@ Mesa's not the solution.

    2.3 Where is the GLUT library?

    -GLUT (OpenGL Utility Toolkit) is in the separate MesaGLUT-x.y.z.tar.gz file. -If you don't already have GLUT installed, you should grab the MesaGLUT -package and compile it with the rest of Mesa. +GLUT (OpenGL Utility Toolkit) is no longer in the separate MesaGLUT-x.y.z.tar.gz file. +If you don't already have GLUT installed, you should grab +freeglut.

    diff --git a/mesalib/docs/license.html b/mesalib/docs/license.html index 44b980d93..5da8ef1de 100644 --- a/mesalib/docs/license.html +++ b/mesalib/docs/license.html @@ -38,10 +38,10 @@ target="_parent">Silicon Graphics Incorporated.

    The Mesa distribution consists of several components. Different copyrights -and licenses apply to different components. For example, GLUT is copyrighted -by Mark Kilgard, some demo programs are copyrighted by SGI, some of the Mesa -device drivers are copyrighted by their authors. See below for a list of -Mesa's main components and the license for each. +and licenses apply to different components. For example, some demo programs +are copyrighted by SGI, some of the Mesa device drivers are copyrighted by +their authors. See below for a list of Mesa's main components and the license +for each.

    The core Mesa library is licensed according to the terms of the MIT license. diff --git a/mesalib/docs/sourcetree.html b/mesalib/docs/sourcetree.html index 67e0494b1..2e2d1d3f2 100644 --- a/mesalib/docs/sourcetree.html +++ b/mesalib/docs/sourcetree.html @@ -1,166 +1,165 @@ - - -Mesa Source Tree - - - - - -

    Mesa source code tree overview

    - -

    -This is a brief summary of Mesa's directory tree and what's contained in -each directory. -

    - - - - - - - + + +Mesa Source Tree + + + + + +

    Mesa source code tree overview

    + +

    +This is a brief summary of Mesa's directory tree and what's contained in +each directory. +

    + + + + + + + -- cgit v1.2.3