History

Chris Dalton 8854829351 Reland "Prefer the NV_framebuffer_blit extension over ANGLE" This is a reland of `202ce887ec` Original change's description: > Prefer the NV_framebuffer_blit extension over ANGLE > > The ANGLE/CHROMIUM glBlitFramebuffer requires full size blits, which > is really bad for DMSAA. The NV extension does allow blits of > sub-rectangles, so we prefer that one if it's available. > > Bug: skia:12176 > Bug: skia:12177 > Bug: skia:12234 > Bug: skia:12235 > Change-Id: I463ac631fff64ad564f294cf2f26be7410e8c356 > Reviewed-on: https://skia-review.googlesource.com/c/skia/+/430576 > Reviewed-by: Greg Daniel <egdaniel@google.com> > Commit-Queue: Chris Dalton <csmartdalton@google.com> Bug: skia:12176 Bug: skia:12177 Bug: skia:12234 Bug: skia:12235 Change-Id: I41d062f9894f5a81c78a37de27a288bc17812643 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/431817 Reviewed-by: Greg Daniel <egdaniel@google.com> Commit-Queue: Chris Dalton <csmartdalton@google.com>		2021-07-23 16:20:36 +00:00
..
gen_interface.go
interface.json5	Reland "Prefer the NV_framebuffer_blit extension over ANGLE"	2021-07-23 16:20:36 +00:00
Makefile
README.md
templates.go	Don't cast emscripten pointers when assembling WebGL interface	2020-09-30 14:31:07 +00:00

README.md

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.