Just an idle thought in passing .... with the advent of 64 bit builds, it may not be such a good idea to mark a "long" as a 32 bit quantity since I believe the redmond 64 bit model defines long as a 64 bit quantity where as an int is 32 bits. On 32 bit systems, the two are the same size and can be freely interchanged. So apply the patch but ensure the build is 32 bits only.
Happy New Year PhilT -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Somerville, Andrew Sent: 09 January 2008 21:43 To: osg-users@lists.openscenegraph.org Subject: [osg-users] INT32 redeifinition with Win32 and VS8 binary package It appears that the VS8 binary package for osg2.2.0 has a problem in one of the 3rd party header files included. (jmorecfg.h) Compiling against it causes an error regarding redefinition of INT32. Im not sure if there are any repercussions, but there is a simple fix seen in an old patch on the secondlife wiki which protects the define with a check against WIN32 https://wiki.secondlife.com/wiki/Patch_jpeglib in jmorecfg.h: #ifndef XMD_H typedef long INT32; #endif is changed to: #if !defined( XMD_H ) && !defined( WIN32 ) typedef long INT32; #endif It also does an #undef on FAR just before it blanks it to remove a warning about redifinition. Im not sure how hard it would be to repackage the current 2.2 VS8 binary package, but at least it can be fixed for for future Visual Studio packages. Regards, Andy _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
