I'm finding may here from Github (https://github.com/dcnieho/FreeGLUT/issues/new)
I'm trying to use/try FreeGLUT without completely abandoning classic GLUT. I don't quite understand why FreeGLUT uses different macros for things like GLUTAPIENTRY which become FGLUTAPIENTRY?
It's fine for bookkeeping but there needs to be a #define GLUTAPIENTRY FGLUTAPIENTRY somewhere right?
Another problem is "APIENTRY" on Windows means __stdcall and that is how classic GLUT defines it. It's strange because FreeGLUT defines it as such if the shared library is used, but not with static library. It expressly doesn't define it.
Maybe this is more of a feature request, or plea for sanity (it's not a big deal but improvements are good for everyone) but having as an end-user to do the likes of:
#ifndef GLUTAPIENTRY
#define GLUTAPIENTRY FGLUTAPIENTRY
#endif
For these things is a minor nuisance. And not using __stdcall is not in keeping with GLUT or Windows. As far as I know these are just calling conventions with no special benefit for cross-module calls. The only good reason for GLUT to have used them is if the functions are passed to Win32 APIs that expect this, in which case if FreeGLUT needed to do this it would have to write wrapping delegation objects. I understand if it can't be changed now, so I should just stop typing :)
Anyway, even if not documented GLUTAPIENTRY is as much part of the GLUT API as glutMainLoop.
I meant https://github.com/dcnieho/FreeGLUT/issues/52
I made a special point to copy/paste that and did not PASTE! Can't seem to edit these things. Funny :)
EDITED: Sorry again, I meant to say FGAPIENTRY. Also the following is easier:
Last edit: Mick P. 2017-05-23