As Bert indicated, it's not really relevant but since you asked...

I believe the OpenGL API calls were generated by code written by Andreas
Raab 15+ years ago against the OpenGL spec files (these are files from the
Khronos Group which have not been maintained for modern OpenGL releases).
When I asked about this over a decade ago, he responded indicating what I
just wrote and that he no longer had the code he used to generate them.

If you were to do it again today, you would want to use the OpenGL C header
files instead.  But again this is somewhat moot regarding Croquet: it's
written against an ancient version of OpenGL (I believe 1.6 + extensions
that get it *roughly* to 2.0 feature-wise) which most desktop drivers are
still backwards compatible with.  So you can just use the calls already
there.  You'd really only need to worry about regenerating the API if you
wanted to update Croquet to take advantage of the latest OpenGL/features
and/or run it under OpenGL ES.  This would not be a trivial task since
you'd probably have to rewrite, or at least significantly restructure, most
of Croquet to make it work.

On Wed, Mar 11, 2020 at 5:58 PM gettimothy via Squeak-dev <
squeak-dev at lists.squeakfoundation.org> wrote:

> btw, the glMatrixMode:mode method tells us that it was automatically
> generated.
>
> by what? When? against what?
>
> glMatrixMode: mode
> *"This method was automatically generated."*
> "void glMatrixMode(GLenum mode);"
> <apicall: void 'glMatrixMode' (ulong) module: '#openGLLibraryName'>
> ^self externalCallFailed
>
>
> Is that "automatic generation"  an example of fundamental work that must
> be done to make Croquet rock-n-roll?
>
> cheers,
>
> tty
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20200311/af6e4a22/attachment.html>