Re: --without-opengl problems
* On Mon, 29 May 2006, Eric Pouech wrote: > * Saulius Krasuckas wrote: > > > > Shouldn't configure delete dlls/wined3d/wined3d.dll.so or unlink > > dlls/wined3d.dll.so or at least define code don't try loading > > wined3d.dll when "--without-opengl" option is given to it? > > > > IOW, "make clean" shouldn't be necessary here, right? > > The configure system is not robust enough to allow the changes you're talking > off. If you change the options passed to ./configure, then you need to rebuild > everything from scratch. Period. > Make distclean is even preferable to make clean. Thanks :)
Re: --without-opengl problems
Am Montag, 29. Mai 2006 15:46 schrieb Jakob Eriksson: > Off-topic, has anyone run Wine with this? > http://bugle.sourceforge.net/ > > It checks OpenGL calls for validity. I use it sometimes to find out which calls WineD3D does to debug rendering problems. It's quite nice combined with wine traces pgpg7Ug5ayWMi.pgp Description: PGP signature
Re: --without-opengl problems
Off-topic, has anyone run Wine with this? http://bugle.sourceforge.net/ It checks OpenGL calls for validity. regards, Jakob Saulius Krasuckas wrote: If I compile Wine by starting with "./configure", it builds dlls/wined3d/wined3d.dll.so file. Then If I run some Ogre (d3d) game, I get all video setup stuff OK. If I connect to my tightvnc server after and run the game here, I get Xlib errors in the output (about missing GLX on :1.0 or a like). Then I decide to disable OpenGL support in Wine and start with "./configure --without-opengl". After this the wined3d.dll.so is left on the disk. And if later I run the game again via vnc server, I get weird errors and see Wine crashing in wined3d.dll (and sometimes wineprefixcreate crashes inside shlwapi.dll or opengl.dll). Isn't this behaviour strange a bit? Shouldn't configure delete dlls/wined3d/wined3d.dll.so or unlink dlls/wined3d.dll.so or at least define code don't try loading wined3d.dll when "--without-opengl" option is given to it? IOW, "make clean" shouldn't be necessary here, right? Well, I just may be missing some information... TIA
Re: --without-opengl problems
Saulius Krasuckas wrote: If I compile Wine by starting with "./configure", it builds dlls/wined3d/wined3d.dll.so file. Then If I run some Ogre (d3d) game, I get all video setup stuff OK. If I connect to my tightvnc server after and run the game here, I get Xlib errors in the output (about missing GLX on :1.0 or a like). Then I decide to disable OpenGL support in Wine and start with "./configure --without-opengl". After this the wined3d.dll.so is left on the disk. And if later I run the game again via vnc server, I get weird errors and see Wine crashing in wined3d.dll (and sometimes wineprefixcreate crashes inside shlwapi.dll or opengl.dll). Isn't this behaviour strange a bit? Shouldn't configure delete dlls/wined3d/wined3d.dll.so or unlink dlls/wined3d.dll.so or at least define code don't try loading wined3d.dll when "--without-opengl" option is given to it? IOW, "make clean" shouldn't be necessary here, right? Well, I just may be missing some information... TIA The configure system is not robust enough to allow the changes you're talking off. If you change the options passed to ./configure, then you need to rebuild everything from scratch. Period. Make distclean is even preferable to make clean. Another options is to have one compilation directory for each set of options to configure you want to use (assuming you're running wine from the build tree). A+
--without-opengl problems
If I compile Wine by starting with "./configure", it builds dlls/wined3d/wined3d.dll.so file. Then If I run some Ogre (d3d) game, I get all video setup stuff OK. If I connect to my tightvnc server after and run the game here, I get Xlib errors in the output (about missing GLX on :1.0 or a like). Then I decide to disable OpenGL support in Wine and start with "./configure --without-opengl". After this the wined3d.dll.so is left on the disk. And if later I run the game again via vnc server, I get weird errors and see Wine crashing in wined3d.dll (and sometimes wineprefixcreate crashes inside shlwapi.dll or opengl.dll). Isn't this behaviour strange a bit? Shouldn't configure delete dlls/wined3d/wined3d.dll.so or unlink dlls/wined3d.dll.so or at least define code don't try loading wined3d.dll when "--without-opengl" option is given to it? IOW, "make clean" shouldn't be necessary here, right? Well, I just may be missing some information... TIA
