minor info update

[mesa.git] / docs / osmesa.html

diff --git a/docs/osmesa.html b/docs/osmesa.html
index ace42001131976356b43aa17cb36317a06c9f97c..6ed3c5e710d2375f213bb081c6c5b1857bca1b16 100644 (file)
--- a/docs/osmesa.html
+++ b/docs/osmesa.html
@@ -37,32 +37,33 @@ memory.
    accuracy (film and IBR, for example).  If you're in this situation
    you'll be happy to know that Mesa supports 16-bit and 32-bit color
    channels through the OSMesa interface.  When using 16-bit channels,
-   channels are GLushorts and pixels occupy 8 bytes.  When using 32-bit
-   channels, channels are GLfloats and pixels occupy 16 bytes.
+   channels are GLushorts and RGBA pixels occupy 8 bytes.  When using 32-bit
+   channels, channels are GLfloats and RGBA pixels occupy 16 bytes.
 </p>
 <p>
    To build Mesa/OSMesa with 16-bit color channels:
 <pre>
-      cd Mesa-4.x/src
-      make -f Makefile.X11 clean
-      make -f Makefile.OSMesa16 linux-osmesa16
+      make realclean
+      make linux-osmesa16
 </pre>
 
    For 32-bit channels:
 <pre>
-      cd Mesa-4.x/src
-      make -f Makefile.X11 clean
-      make -f Makefile.OSMesa16 linux-osmesa32
+      make realclean
+      make linux-osmesa32
 </pre>
 
 <p>
-If you're not using Linux, you can easily edit Make-config and add
-an appropriate configuration.
+You'll wind up with a library named libOSMesa16.so or libOSMesa32.so.
 </p>
+
 <p>
-The Mesa/tests/osdemo16.c file (available via CVS) demonstrates how
-to use this feature.
+If you need to compile on a non-Linux platform, copy Mesa/configs/linux-osmesa16
+to a new config file and edit it as needed.  Then, add the new config name to
+the top-level Makefile.  Send a patch to the Mesa developers too, if you're
+inclined.
 </p>
+
 <p>
 BE WARNED: 16 and 32-bit channel support has not been exhaustively
 tested and there may be some bugs.  However, a number of people have