aboutsummaryrefslogtreecommitdiffstats
path: root/docs/devinfo.html
diff options
context:
space:
mode:
authorBrian Paul <[email protected]>2006-09-21 22:53:15 +0000
committerBrian Paul <[email protected]>2006-09-21 22:53:15 +0000
commitbb0862968e1915852a011cd296ec6918b1142518 (patch)
treeaa94a419b07eaefbbdab97fce0e5c9540a438098 /docs/devinfo.html
parent60955d7f96952e3815438711d8b595c63899972d (diff)
updated extension info
Diffstat (limited to 'docs/devinfo.html')
-rw-r--r--docs/devinfo.html14
1 files changed, 9 insertions, 5 deletions
diff --git a/docs/devinfo.html b/docs/devinfo.html
index 4d4730be757..cce14d73a36 100644
--- a/docs/devinfo.html
+++ b/docs/devinfo.html
@@ -34,11 +34,15 @@ To add a new GL extension to Mesa you have to do at least the following.
corresponding Python scripts.
</li>
<li>
- 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 <code>gl_extensions</code> struct in mtypes.h
+</li>
+<li>
+ Update the <code>extensions.c</code> file.
+</li>
+<li>
+ 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.
</li>
<li>
If the new extension adds new GL state, the functions in get.c, enable.c