Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. Library 'vulkan' is not defined. with QMake, clang6, Qt 5.10.1
Forum Updated to NodeBB v4.3 + New Features

Library 'vulkan' is not defined. with QMake, clang6, Qt 5.10.1

Scheduled Pinned Locked Moved Solved Installation and Deployment
7 Posts 3 Posters 2.0k Views 1 Watching
  • 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.
  • H Offline
    H Offline
    Hallot
    wrote on last edited by
    #1

    Hi,

    I've just upgraded to clang6, and my qmake projects with Qt 5.10.1 all fail to configure now with the error:
    "Library 'vulkan' is not defined."

    I have no issues with GCC 7.3 or with CMake based projects.

    I've noticed that "#define QT_FEATURE_vulkan 1" has been set to 1 now, where it was -1 before, but even changing it to -1 manually does not seem to fix the issue.

    Any help is appreciated,
    Thanks.

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #2

      Hi,

      Do you mean that the vulkan option gets activated only when building with clang ?

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      1 Reply Last reply
      0
      • H Offline
        H Offline
        Hallot
        wrote on last edited by
        #3

        I don't think the option is activated only with Clang, the macro I talked about is a system include and thus would not change between compilers.
        Maybe there's something missing in the clang toolchain? Or maybe it's an option that Clang triggers and not GCC.
        I am not sure really. And I'm not sure how to check whether the Vulkan option is activated with GCC.

        1 Reply Last reply
        0
        • SGaistS Offline
          SGaistS Offline
          SGaist
          Lifetime Qt Champion
          wrote on last edited by
          #4

          Can you explain exactly how you setup things ?

          Interested in AI ? www.idiap.ch
          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

          1 Reply Last reply
          0
          • G Offline
            G Offline
            geomojo
            wrote on last edited by
            #5

            I came across this error too (haven't looked for a work around yet). Anyway, SGaist asked how to set things up to get this error, so thought I'd share...

            1. Start a VS command prompt (I'm using VS2017)
              C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\Tools\LaunchDevCmd.bat

            2. Set QMAKESPEC
              set QMAKESPEC=winrt-x64-msvc2017

            3. Run qmake
              qmake -tp vc

            I get "Project ERROR: Library 'vulkan' is not defined". This has something to do with the "winrt-x64-msvc2017" part (I think). I'm able to run qmake OK with other values for QMAKESPEC.

            1 Reply Last reply
            0
            • SGaistS Offline
              SGaistS Offline
              SGaist
              Lifetime Qt Champion
              wrote on last edited by
              #6

              Based on this blog post Vulkan is not available for WinRT in Qt 5.10.

              Interested in AI ? www.idiap.ch
              Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

              1 Reply Last reply
              0
              • H Offline
                H Offline
                Hallot
                wrote on last edited by
                #7

                Yes, I've managed to solved this by correctly setting the makespec as well. I think it was using old spec files for a previous Qt/Clang version which caused the non-obvious issue.

                Thanks for the help.

                1 Reply Last reply
                0

                • Login

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Users
                • Groups
                • Search
                • Get Qt Extensions
                • Unsolved