Re: [gl4java-usergroup] GC Bug

[Pepijn V. E. <pep...@lu...>]

I tried adding my implementations to the manual files. But, as I 
expected, the generated file contained .c file contained two 
implementations of the same mehtod. In the makefile, the manual and auto 
generated files get pasted together using cat which explains the double 
implementation.
I can't find anything that suggests glGetString gets a special treatment 
in the C2J code.
Any ideas?

Pepijn Van Eeckhoudt

Kenneth B. Russell wrote:

>>I wrote a simple memory management module that keeps track of the
>>alocated arrays, so they can be released at a later point. I've tested
>>this idea with the tesselation stuff, and it works fine.
>>I've made these changes to the C files in the CNativeCode directory,
>>which isn't ideal (should be autogenerated). Could someone explain to me
>>where I can put my implementations of the
>>Java_gl4java_GLUFunc14JauJNI_gluTessVertex__* functions, so they would
>>appear in the generated c files automatically.
>>
> 
> These files are built by C2J. Sven can answer this better, but
> you're going to have to add them to something like
> C2J/gl-manualCodedImplJNI.c. The important thing is to then
> exclude them from the autogeneration process. I'm not sure
> whether simply adding the prototype to gl-manualCoded.orig.h will
> cause C2J to ignore the function; see how glGetString is handled
> in the Mesa header files and in the C2J Makefile.
> 
> _______________________________________________
> gl4java-usergroup mailing list
> gl4...@li...
> https://lists.sourceforge.net/lists/listinfo/gl4java-usergroup
> 
>