1 This directory contains several helper scripts that facilitate the generation
2 of the API descriptions from specs and/or header files.
4 The specs/headers are not expressive enough, which is why we can't just code
5 generate everything from them directly. However the scripts in this directory
6 usually get 90% of the work done automatically.
12 For OpenGL the typical procedure is to run
16 which will generate several python scripts with prototypes and defines from the
17 Khronos `.spec` files:
29 and then manually crossport new functions / enums to the identically named
30 files in the parent dir via a side-by-side diff tool, such as gvimdiff.
36 Khronos doesn't provide `.spec` files for OpenGL ES. But the `gltxt.py` script
37 can extract and convert prototypes for the `.txt` extension specifications:
39 $ ./gltxt.py http://www.khronos.org/registry/gles/extensions/OES/OES_mapbuffer.txt
41 GlFunction(Void, "glGetBufferPointervOES", [(GLenum, "target"), (GLenum, "pname"), (OpaquePointer(OpaquePointer(Void)), "params")], sideeffects=False),
42 GlFunction(OpaquePointer(Void), "glMapBufferOES", [(GLenum, "target"), (GLenum, "access")]),
43 GlFunction(GLboolean, "glUnmapBufferOES", [(GLenum, "target")]),
49 When the domain specific scripts don't work the fallback solution is `cdecl.py`, which can parse most C declarations:
51 $ echo 'void *memcpy(void *dest, const void *src, size_t n);' | ./cdecl.py
52 Function(OpaquePointer(Void), "memcpy", [(OpaquePointer(Void), "dest"), (OpaquePointer(Const(Void)), "src"), (size_t, "n")]),