[Wine] Re: Making wine use the correct OpenGL libraries

raziel2001au wineforum-user at winehq.org
Sat Sep 5 03:53:57 CDT 2009


Sorry, but I can't agree with you there... firstly, I haven't run into the 64-bit compilation issue you've mentioned at all - it seems to automatically set -m32 for me.

With regards to OpenGL, I would say it is very much broken because it refuses to use the OpenGL library file it should be using. If you do a ./configure (without parameters), it should automatically pick up the correct library/headers, but on Snow Leopard it doesn't. The header issue can be fixed with a -I/usr/X11/include. At this point it picks up GL libraries automatically, but it picks up libGL.1.dylib, which is NOT the correct library, it should be using the one in the frameworks folder (libGL.dylib), otherwise you'll run into the situation where you have to specify library fallback paths for it to work. On top of this, it is not guaranteed to work on other systems, if another user only has libGL.dylib, it won't work. You can force it to look in /System/Library/Frameworks/OpenGL.framework/Libraries, but it refuses to see libGL.dylib, which is the library it should be using. It really just skips over it for some reason. If I'm not mistaken I think the full path to that file is even hardcoded in the configure script - but it gets skipped and picks libGL.1.dylib instead.

The reason you have to enter a fallback library path is because your compiles are not using the correct GL library, as in, the one in the OpenGL.framework folder. If you compile under Leopard and transfer the binaries over to Snow Leopard, you do not need to specify fallback library paths or anything ridiculous like that - it just works and the result is transferrable to other Mac systems.







More information about the wine-users mailing list