And for the records: As far as i understand by now the glex lib (if present) just wraps wglGetProcAddress (or similar) which in turn resolves the addresses if the various extensions via their name. So it should just be a matter of calling this getprocaddress function with the correct parameters.
Till Am Freitag 09 März 2012 schrieb Kimmo Hämäläinen: > glext.h looks like driver-specific extensions, am I right (at least the > internet seems to tell so)? So there is no guarantee if the driver has > them or not... > > -Kimmo > > On 03/07/12 17:28, ext Till Harbaum / Lists wrote: > > Hi, > > > > i can't figure out how to use glext on n900 or on the n950 using gles1. > > > > As a start i'd just like to access > > glGenFramebuffers() and > > glDeleteFramebuffers() > > > > The only references to this is in GLES/glext.h and the prototypes have > > are named glGenFramebuffersOES and glDeleteFramebuffersOES . So far > > so good. I can compile this. > > > > But i cannot link it. Against what am i supposed to link gles1 applications > > using glext? > > > > Regards, > > Till > > > > -- > > Dr. Till Harbaum<li...@harbaum.org> > > _______________________________________________ > > maemo-developers mailing list > > maemo-developers@maemo.org > > https://lists.maemo.org/mailman/listinfo/maemo-developers > > > > _______________________________________________ > maemo-developers mailing list > maemo-developers@maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-developers > _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
