5509dac4cc
This reverts commit573cb87a07
. Reason for revert: Marking failing validation as optional and filing bug for follow up in Chrome. Original change's description: > Revert "Generate GrGLInterface and GrGlAssembleInterface* from table" > > This reverts commit93b3dce89d
. > > Revert "Delete old assembleInterface code" > > This reverts commit7b1cf20d47
. > > Revert "Delete in favor of autogenerated file" > > This reverts commit0223bd01d8
. > > Bug: skia:8474 > NOTRY:true > Change-Id: I23a904347f9d6cefd1710a2de056c39d52f4b178 > Reviewed-on: https://skia-review.googlesource.com/c/skia/+/203463 > Reviewed-by: Stan Iliev <stani@google.com> > Commit-Queue: Stan Iliev <stani@google.com> TBR=kjlubick@google.com,stani@google.com Change-Id: I85adb302eb093fe9b7a4ec2c984323c191278a43 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: skia:8474 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/203177 Reviewed-by: Kevin Lubick <kjlubick@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
760 B
760 B
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.