You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of my lasting concerns is the side of the wrappers generated by Glow. For instance Azul3D has an OpenGL 2 renderer (http://github.com/azul3d/gfx-gl2) that uses a somewhat small subset of the OpenGL 2.0 API.
Since most of the symbols (enums and functions) generated by Glow are not actually used by us -- it seems silly to compile them at all. I'd like to be able to specify a JSON input file to Glow that would specify the symbols that we actually want, for example:
And Glow could generate just those symbols, greatly reducing the compilation time. Although I think it's not strictly the same tactic -- this could also help others trying to deal with issue #23
The text was updated successfully, but these errors were encountered:
One of my lasting concerns is the side of the wrappers generated by Glow. For instance Azul3D has an OpenGL 2 renderer (http://github.com/azul3d/gfx-gl2) that uses a somewhat small subset of the OpenGL 2.0 API.
Since most of the symbols (enums and functions) generated by Glow are not actually used by us -- it seems silly to compile them at all. I'd like to be able to specify a JSON input file to Glow that would specify the symbols that we actually want, for example:
And Glow could generate just those symbols, greatly reducing the compilation time. Although I think it's not strictly the same tactic -- this could also help others trying to deal with issue #23
The text was updated successfully, but these errors were encountered: