A few people have been trying to build FTGL on Leopard and getting this. Anyone have any ideas?
/sw/src/fink.build/ftgl-2.1.2-3/FTGL/mac/build/FTGL.build/Default/ ftgl.build/Objects-normal/i386/FTVectoriser.o /sw/src/fink.build/ftgl-2.1.2-3/FTGL/src/FTVectoriser.cpp: In member function 'void FTVectoriser::MakeMesh(FTGL_DOUBLE)': /sw/src/fink.build/ftgl-2.1.2-3/FTGL/src/FTVectoriser.cpp:186: error: invalid conversion from 'GLvoid (*)(...)' to 'GLvoid (*)()' /sw/src/fink.build/ftgl-2.1.2-3/FTGL/src/FTVectoriser.cpp:186: error: initializing argument 3 of 'void gluTessCallback(GLUtesselator*, GLenum, GLvoid (*)())' /sw/src/fink.build/ftgl-2.1.2-3/FTGL/src/FTVectoriser.cpp:187: error: invalid conversion from 'GLvoid (*)(...)' to 'GLvoid (*)()' /sw/src/fink.build/ftgl-2.1.2-3/FTGL/src/FTVectoriser.cpp:187: error: initializing argument 3 of 'void gluTessCallback(GLUtesselator*, GLenum, GLvoid (*)())' /sw/src/fink.build/ftgl-2.1.2-3/FTGL/src/FTVectoriser.cpp:188: error: invalid conversion from 'GLvoid (*)(...)' to 'GLvoid (*)()' /sw/src/fink.build/ftgl-2.1.2-3/FTGL/src/FTVectoriser.cpp:188: error: initializing argument 3 of 'void gluTessCallback(GLUtesselator*, GLenum, GLvoid (*)())' /sw/src/fink.build/ftgl-2.1.2-3/FTGL/src/FTVectoriser.cpp:189: error: invalid conversion from 'GLvoid (*)(...)' to 'GLvoid (*)()' /sw/src/fink.build/ftgl-2.1.2-3/FTGL/src/FTVectoriser.cpp:189: error: initializing argument 3 of 'void gluTessCallback(GLUtesselator*, GLenum, GLvoid (*)())' /sw/src/fink.build/ftgl-2.1.2-3/FTGL/src/FTVectoriser.cpp:190: error: invalid conversion from 'GLvoid (*)(...)' to 'GLvoid (*)()' /sw/src/fink.build/ftgl-2.1.2-3/FTGL/src/FTVectoriser.cpp:190: error: initializing argument 3 of 'void gluTessCallback(GLUtesselator*,
.hc
------------------------------------------------------------------------ ----
Using ReBirth is like trying to play an 808 with a long stick. - David Zicarelli
Leopard use the unix def i change FTVectoriser.cpp like this
#ifdef __APPLE_CC__ typedef GLvoid (*GLUTesselatorFunction)(); #elif defined( __mips ) || defined( __linux__ ) || defined( __FreeBSD__ ) || defined( __OpenBSD__ ) || defined( __sun ) || defined (__CYGWIN__) typedef GLvoid (*GLUTesselatorFunction)(); #elif defined ( WIN32) typedef GLvoid (CALLBACK *GLUTesselatorFunction)( ); #else #error "Error - need to define type GLUTesselatorFunction for this platform/compiler" #endif Am 19.12.2007 um 07:25 schrieb Hans-Christoph Steiner:
invalid conversion from 'GLvoid (*)(...)' to 'GLvoid (*)()'
Matthias Neuenhofer wrote:
Leopard use the unix def i change FTVectoriser.cpp like this
#ifdef __APPLE_CC__ typedef GLvoid (*GLUTesselatorFunction)(); #elif defined( __mips ) || defined( __linux__ ) || defined( __FreeBSD__ ) || defined( __OpenBSD__ ) || defined( __sun ) || defined (__CYGWIN__) typedef GLvoid (*GLUTesselatorFunction)();
so what exactly is the difference between apple and the rest of unix here? wouldn't it be easier to just add "|| defined (__APPLE__)"
or do i misread something?
fmf.a IOhannes
Matthias Neuenhofer wrote:
Leopard use the unix def i change FTVectoriser.cpp like this #ifdef __APPLE_CC__ typedef GLvoid (*GLUTesselatorFunction)(); #elif defined( __mips ) || defined( __linux__ ) || defined( __FreeBSD__ ) || defined( __OpenBSD__ ) || defined( __sun ) || defined (__CYGWIN__) typedef GLvoid (*GLUTesselatorFunction)();
so what exactly is the difference between apple and the rest of unix here? wouldn't it be easier to just add "|| defined (__APPLE__)"
or do i misread something?
fmf.a IOhannes
Yes this will be easier, but maybe there is a way to define the different Mac OS´s?
lg mn
On Dec 19, 2007, at 9:29 AM, Matthias Neuenhofer wrote:
Matthias Neuenhofer wrote:
Leopard use the unix def i change FTVectoriser.cpp like this #ifdef __APPLE_CC__ typedef GLvoid (*GLUTesselatorFunction)(); #elif defined( __mips ) || defined( __linux__ ) || defined( __FreeBSD__ ) || defined( __OpenBSD__ ) || defined( __sun ) || defined (__CYGWIN__) typedef GLvoid (*GLUTesselatorFunction)();
so what exactly is the difference between apple and the rest of unix here? wouldn't it be easier to just add "|| defined (__APPLE__)"
or do i misread something?
fmf.a IOhannes
Yes this will be easier, but maybe there is a way to define the different Mac OS´s?
I am pretty sure that __APPLE__ is the gcc macro for Mac OS X. __APPLE__ wasn't used on MacOS 9 and earlier since gcc didn't work on that platform.
http://www.winehq.org/pipermail/wine-patches/2003-July/006906.html
.hc
------------------------------------------------------------------------ ----
Man has survived hitherto because he was too ignorant to know how to realize his wishes. Now that he can realize them, he must either change them, or perish. -William Carlos Williams
-
Hans-Christoph Steiner -
IOhannes m zmoelnig -
Matthias Neuenhofer