From: <pau...@no...> - 2009-06-15 07:11:22
|
Hi John, That's exactly what it is - replacement of the OpenWatcom IDE project files (which never worked as they weren't in the right directory structure) with Makefile.wat which allows building from the command line using wmake. I appreciate that there may not be any other OW users on the list who can verify this work, so even if the new makefile cannot be accepted, it would be good if the broken project files could be removed (better no OW support than broken OW support). Regards, Paul -----Original Message----- From: Fay, John F Dr CTR USAF AFMC 46 SK [mailto:joh...@eg...] Sent: Friday, June 12, 2009 8:36 PM To: FreeGLUT developers list Subject: Re: [Freeglut-developer] Updated OpenWatcom support patch OK, I'm confused; I've been out of the loop for a while. Do I put the patch in? It appears to be the deletion of a couple of files and the addition of another one. John F. Fay Technical Fellow Jacobs Technology TEAS Group 850-883-1294 -----Original Message----- From: pau...@no... [mailto:pau...@no...] Sent: Thursday, June 11, 2009 3:35 AM To: fre...@li... Subject: Re: [Freeglut-developer] Updated OpenWatcom support patch So attached is an updated patch for OpenWatcom support - is there anyone who will apply it for me? -----Original Message----- From: Sven Panne [mailto:Sve...@ae...] Sent: Thursday, June 11, 2009 9:25 AM To: Paul Blew; fre...@li... Subject: Re: [Freeglut-developer] Updated OpenWatcom support patch Am Montag, 8. Juni 2009 09:30:44 schrieb pau...@no...: > The problem manifests itself as a compilation error (see attached). > It is complaining that the arguments for __glutInitWithExit do not > match those in the prototype. > > It's been a while since I used classic GLUT, but I have a dim and > distant memory that it was a problem there too. It seems that there is > an assumption that if you are on Windows you must be using MSVC. > > A simple fix would be changing line 602 from: > > #if defined(_WIN32) && !defined(GLUT_DISABLE_ATEXIT_HACK) > > to either: > > #if defined(_WIN32) && !defined(GLUT_DISABLE_ATEXIT_HACK) && > !defined(__WATCOMC__) > > or: > > #if defined(_MSC_VER) && !defined(GLUT_DISABLE_ATEXIT_HACK) OK, now I understand the problem: For some obscure reason, Watcom uses a different, non-standard calling convention for C's "exit" function ("watcall" vs. "cdecl") than all other C runtimes. This leads to a mismatch in our prototype and even more problems in classic GLUT. I think doing this differently is a very, very bad idea from Watcom, so I'm simply disabling the atexit hack for Watcom only, i.e. use the first fix you proposed. The reason for fixing it this way is that we stay as close to original GLUT as possible. I don't know e.g. is the atexit hack is necessary for other development environments/runtimes, e.g. MinGW, so let's be conservative... Anyway, this was no show stopper, so where is our 2.6.0 release? :-( Cheers, S. ---------------------------------------------------------------------------- -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Freeglut-developer mailing list Fre...@li... https://lists.sourceforge.net/lists/listinfo/freeglut-developer |