On Sunday, November 17, 2002, at 07:55  AM, Andreas.Raab at gmx.de wrote:

> Hi John,
>
> This is great! Thanks a lot for your help. Incidentally, with all the  
> flurry
> of GLX<InsertYourPlatformHere> I guess I should really build some sort  
> of
> OpenGL plugin which simply links against the host libs. Bert, John, Is  
> this a
> problem on any of your platforms (e.g., is there a need to link  
> against GL at
> runtime rather than compile time)?!
>
> Cheers,
>   - Andreas

Well keeping this stuff as a FFI call would be nicer. Once it gets into  
a library, then the VM builders have to
make new VM or plugins for fixes or changes & additions. If the call is  
via FFI then any squeaker can fix it and distribute a change set.

I think the only issue is that various platforms have different names  
for the module. Usually the api name, parm types etc are the same.
So can one substitute an instance variable here for example for that  
hard coded 'OpenGLLibrary'? That for example is the only difference  
between the OS9 and OSX version of the openGL interface class.

glActiveTextureARB: texture
	"This method was automatically generated."
	"void glActiveTextureARB(GLenum texture);"
	<apicall: void 'glActiveTextureARB' (ulong) module: 'OpenGLLibrary'>
	^self externalCallFailed

Ah on the mac, stubs are statically linked in, then resolved to the  
real address dynamically at runtime.


> --
======================================================================== 
===
John M. McIntosh <johnmci at smalltalkconsulting.com> 1-800-477-2659
Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
======================================================================== 
===