Split repo in generator and generated Zig files

[fabioarnold]

It would be nice to keep the generated Zig files in a separate and lean repo so they can be easily included using package managers like gyro and zigmod.

[ikskuh]

I guess the best solution would actually be a online tool where you can build your own wrapper, and just download the result file

[desttinghim]

Has this split already taken place? The repo no longer seems to contain the generated files.

[ikskuh]

I would not do a split, but upload generated files via GitHub CI. Thing is that we don't really know what users need in terms of extensions and such. So we either have to decide on default extensions (like GL_ARB_direct_state_access and KHR_debug) or we just ship without any.

Also do we ship a single package with all modules or one module per combination?

If someone would do a web server, we could ship them with caching enabled, so just generate once (or every time on download)