7ae444449c
This logic looks to have been dropped when we moved to the auto generated interfaces Bug: skia:11083 Change-Id: I5069d81c872ed2c084b8ddf773f63e5202b123eb Reviewed-on: https://skia-review.googlesource.com/c/skia/+/348190 Reviewed-by: Kevin Lubick <kjlubick@google.com> Reviewed-by: Brian Salomon <bsalomon@google.com> Commit-Queue: Greg Daniel <egdaniel@google.com> |
||
|---|---|---|
| .. | ||
| gen_interface.go | ||
| interface.json5 | ||
| Makefile | ||
| README.md | ||
| templates.go | ||
GrGlInterface Autogeneration
Background
At a high level, the first three steps of making a GrGLInterface (a generic way to interact with a GL-like GPU) are:
- Assemble: Copy a set of function pointers into the struct
- Validate: Make sure the function pointers advertised actually exist.
- Capabilities: Compute what fast/slow paths are enabled based on the functions in the struct (GrGLCaps, for short)
Autogeneration
The first two steps have been automated with a table-based generation script located in this folder. The table is in JSON5 format (like JSON, but with comments). O
Once edited, the Assemble/Validate code can be re-generated by running
make generate in this folder.