compiling wine (wow64) with opengl 1.3
Hello, I'd like testing some cross-compile qt5 applications, in the past I was able to use wine for testing. However, recently this does not work anymore, the application runs on windows but crashes on wine (if you want, I can send details ). I suspect that recent versions of qt5 require opengl 1.3. Therefore, I'm trying to compile wine (actually wow64) from source with opengl 1.3 support, and was trying to follow the documentation [1,2]. I'm testing on debian 10 and did apt-get build-dep wine cd ../wine-source/dlls/opengl32 && ./make_opengl 1.3 cd ~/wine-dirs/build64 make distclean ../wine-source/configure --enable-win64 make Configuration complains about the following issues: configure: MinGW compiler not found, cross-compiling PE files won't be supported. configure: libhal 64-bit development files not found, no legacy dynamic device support. configure: libusb-1.0 64-bit development files not found (or too old), USB devices won't be supported. configure: OSS sound system found but too old (OSSv4 needed), OSS won't be supported. I believe these are not relevant. However, compilation fails, the log file is attached). What I'm missing here? What is your recommendation how to address this issue? Cheers, Alois [1] https://wiki.winehq.org/Building_Wine [2] https://wiki.winehq.org/Wine_Developer%27s_Guide/Wine_and_OpenGL
Hi, Am 12.06.20 um 22:50 schrieb Alois Schlögl:
I'd like testing some cross-compile qt5 applications, in the past I was able to use wine for testing. However, recently this does not work anymore, the application runs on windows but crashes on wine (if you want, I can send details ). I suspect that recent versions of qt5 require opengl 1.3. Therefore, I'm trying to compile wine (actually wow64) from source with opengl 1.3 support, and was trying to follow the documentation [1,2]. I'm testing on debian 10 and did
I doubt it has anything to do with OpenGL 1.3. GL 1.3 is ancient, Wine supports way newer GL versions. I suspect that either your host OpenGL is broken (e.g. there are libs to link against but loading the mesa driver or creating a context fails) or your program is not working for some other reason. Afaik Qt internally uses GL:ES, which is provided by ANGLE, which wraps to d3d11, which we then wrap to whatever OpenGL is available. I might be wrong on that though and confuse it with other components that use ANGLE.
Le dimanche 14 juin 2020 à 19:08 +0200, Stefan Dösinger a écrit :
Hi,
Am 12.06.20 um 22:50 schrieb Alois Schlögl:
I'd like testing some cross-compile qt5 applications, in the past I was able to use wine for testing. However, recently this does not work anymore, the application runs on windows but crashes on wine (if you want, I can send details ). I suspect that recent versions of qt5 require opengl 1.3. Therefore, I'm trying to compile wine (actually wow64) from source with opengl 1.3 support, and was trying to follow the documentation [1,2]. I'm testing on debian 10 and did
I doubt it has anything to do with OpenGL 1.3. GL 1.3 is ancient, Wine supports way newer GL versions. I suspect that either your host OpenGL is broken (e.g. there are libs to link against but loading the mesa driver or creating a context fails) or your program is not working for some other reason.
Afaik Qt internally uses GL:ES, which is provided by ANGLE, which wraps to d3d11, which we then wrap to whatever OpenGL is available. I might be wrong on that though and confuse it with other components that use ANGLE.
Hello, I don't know about Qt but I know this bug related to ANGLE: https://bugs.winehq.org/show_bug.cgi?id=44985 Many applications using CEFv3 Angle OpenGL ES 2.0 for H/W Accelerated Canvas and WebGL display blank/black windows (disabling or removing 'libglesv2.dll' is a workaround) Regards. -- Olivier F. R. Dierick o.dierick(a)piezo-forte.be
On Fri, 12 Jun 2020, Alois Schlögl wrote: [...]
Configuration complains about the following issues:
configure: MinGW compiler not found, cross-compiling PE files won't be supported. configure: libhal 64-bit development files not found, no legacy dynamic device support. configure: libusb-1.0 64-bit development files not found (or too old), USB devices won't be supported. configure: OSS sound system found but too old (OSSv4 needed), OSS won't be supported.
I don't know if it's going to help you but on Debian 10 wt-install-dev can help you get all of these (except libhal which is totally obsolete), and even works around Debian's multiarch support bugs. https://github.com/fgouget/wt-daily/blob/master/wt-install-dev Since you're going to run Wine too I'd recommend running the following as root: wt-install-dev --wine --tests Or if you want to see exactly what it will do: wt-install-dev --wine --tests --packages # then you get to tell apt whether to proceed or abort # and then to work around missing .so symlinks wt-install-dev --wine --tests --workarounds --dry-run # and without --dry-run if that looked ok wt-install-dev --wine --tests --workarounds -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ There are 10 types of people in the world... those who understand binary and those who don't.
Am 6/15/20 um 1:08 PM schrieb Francois Gouget:
On Fri, 12 Jun 2020, Alois Schlögl wrote: [...]
Configuration complains about the following issues:
configure: MinGW compiler not found, cross-compiling PE files won't be supported. configure: libhal 64-bit development files not found, no legacy dynamic device support. configure: libusb-1.0 64-bit development files not found (or too old), USB devices won't be supported. configure: OSS sound system found but too old (OSSv4 needed), OSS won't be supported. I don't know if it's going to help you but on Debian 10 wt-install-dev can help you get all of these (except libhal which is totally obsolete), and even works around Debian's multiarch support bugs.
https://github.com/fgouget/wt-daily/blob/master/wt-install-dev
Since you're going to run Wine too I'd recommend running the following as root:
wt-install-dev --wine --tests
Or if you want to see exactly what it will do:
wt-install-dev --wine --tests --packages # then you get to tell apt whether to proceed or abort
# and then to work around missing .so symlinks wt-install-dev --wine --tests --workarounds --dry-run # and without --dry-run if that looked ok wt-install-dev --wine --tests --workarounds
Dear Francois, thanks for the hint I can confirm that this help to reduce these warnings. In this case, Stefan Dösinger was right; the problem was somewhere else. I was able to fix the problem, and now there is no (glx) error or any wine versions. (FYI: the problem was how the application was compiled and linked, probably with an incompatible dll, and unrelated to glx). Thanks everyone for the help, Alois
participants (4)
-
Alois Schlögl -
Francois Gouget -
Olivier F. R. Dierick -
Stefan Dösinger