Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved

    Qt Academy Launch in California!

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

    Installation and Deployment
    3
    23
    798
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      TopDoozer last edited by

      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 1 Reply Last reply Reply Quote 0
      • jsulm
        jsulm Lifetime Qt Champion @TopDoozer last edited by

        @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.

        https://forum.qt.io/topic/113070/qt-code-of-conduct

        1 Reply Last reply Reply Quote 1
        • T
          TopDoozer last edited by

          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 1 Reply Last reply Reply Quote 0
          • jsulm
            jsulm Lifetime Qt Champion @TopDoozer last edited by

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

            https://forum.qt.io/topic/113070/qt-code-of-conduct

            1 Reply Last reply Reply Quote 0
            • T
              TopDoozer last edited by

              @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 1 Reply Last reply Reply Quote 0
              • jsulm
                jsulm Lifetime Qt Champion @TopDoozer last edited by

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

                https://forum.qt.io/topic/113070/qt-code-of-conduct

                1 Reply Last reply Reply Quote 0
                • T
                  TopDoozer last edited by

                  i ran nmake with this result:
                  0_1559919306508_nmake.png

                  1 Reply Last reply Reply Quote 0
                  • T
                    TopDoozer last edited by

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

                    1 Reply Last reply Reply Quote 0
                    • T
                      TopDoozer last edited by

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

                      1 Reply Last reply Reply Quote 0
                      • T
                        TopDoozer last edited by

                        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:

                        0_1560020236919_source_dir_configure_mingw32_make.png

                        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 1 Reply Last reply Reply Quote 0
                        • jsulm
                          jsulm Lifetime Qt Champion @TopDoozer last edited by

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

                          https://forum.qt.io/topic/113070/qt-code-of-conduct

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post