Running example 'widgets\graphicsview\boxes' under windows7, needs '-opengl desktop' error

SGaist

These are parts of the tests. I currently don't know why it's failing like that however, you really should add -no-make tests to your configure options. AFAIK, you are not going to hack on Qt so it makes little sense to build all Qt's tests to get the build you are looking for.

TopDoozer

I will try the configure with -nomake tests and then run mingw32-make and see what happens. Do i need to revert anything before i run configure and mingw32-make again? BTW thank you for taking the time to help me out here. Highly appreciated.

jsulm

@TopDoozer said in Running example 'widgets\graphicsview\boxes' under windows7, needs '-opengl desktop' error:

Do i need to revert anything before i run configure and mingw32-make again?

You should start from clean state. Best is to use out of source builds.

TopDoozer

OK. So i now created a 'build' folder. Opened a console in that folder and called configure.bat from there. This is the configure.log file:

Command line: -prefix d:\Qt\Qt5.12.3\build -opengl desktop -nomake tests

I do have a configure.log file.... but i cannot upload it and its toolong to post in toto.
There are a couple of configure tests that fail:

executing config test alloca_h

cd /d D:\Qt\Qt5.12.3\build\config.tests\alloca_h && D:\Qt\Qt5.12.3\build\qtbase\bin\qmake.exe "CONFIG -= qt debug_and_release app_bundle lib_bundle" "CONFIG += shared warn_off console single_arch" D:/Qt/Qt5.12.3/build/config.tests/alloca_h
cd /d D:\Qt\Qt5.12.3\build\config.tests\alloca_h && set MAKEFLAGS=& mingw32-make

g++ -c -fno-keep-inline-dllexport -O2 -w -fexceptions -mthreads -DUNICODE -D_UNICODE -DWIN32 -DMINGW_HAS_SECURE_API=1 -I. -ID:\Qt\Qt5.12.3\5.12.3\Src\qtbase\mkspecs\win32-g++ -o main.o main.cpp
main.cpp:2:20: fatal error: alloca.h: No such file or directory
#include <alloca.h>
^
compilation terminated.
Makefile:165: recipe for target 'main.o' failed
mingw32-make: *** [main.o] Error 1
test config.qtbase.tests.alloca_h FAILED

is the first one...

jsulm

@TopDoozer Failing tests are normal. The question is: is any feature you need disabled because of failing tests? If not then just build.

TopDoozer

@jsulm are you suggesting, that build might fail if i try to run it with a feature that might not have passed the configure test (running nmake right now but expecting it to fail again)?

jsulm

@TopDoozer No, it should not fail, but some features will not be built.

TopDoozer

i ran nmake with this result:

TopDoozer

Any idea whats going on, or what i am missing? Anything i can do to provide more information to gain insight into the error?

TopDoozer

Tried to keep it simple and just ran configure followed by nmake. Same error: Unknown module in Qt: bootstrap-private. WTF?

TopDoozer

Tried something else again. went and ran configure in the source directory (Command line: -prefix d:\Qt\Qt5.12.3\build2 -opengl desktop -nomake tests -nomake examples). Then i ran mingw32-make in the Source folder. Thats what i got:

Anyone any idea, what the hell is going on here? I am starting to think Qt might not be worth it anymore trying to get back into, which would be fine crying shame!

jsulm

@TopDoozer Which version of MinGW do you use to compile?