Qt Forum

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

    Update: Forum Guidelines & Code of Conduct

    Added a new compiler to my system...

    Tools
    2
    5
    1804
    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.
    • mzimmers
      mzimmers last edited by

      ...and one of my two projects allows me to select it as a tool chain (in Projects), and the other one of my projects does not.

      What might cause this? Both are C++ projects that build successfully with the supplied MinGW.

      A little more information: in Build Settings -> Manage (Tool chain) I add the identical path to both projects. But upon exiting the Manage window, project M allows me to choose my Tool Chain, and project SG does not. Both projects are using the same version of Qt, and are using equivalent build configurations (debug/release).

      A customer reported today a similar event; he moved a Qt project over to another machine, but that machine doesn't want to let him use MinGW. It instead is selecting a VS compiler for him.

      What's the trick to how this works?

      Thanks...

      1 Reply Last reply Reply Quote 0
      • T
        tobias.hunger last edited by

        Please hover the Qt version in question and check the ABI in the tool tip. Make sure it matches the ABI set/detected on your compiler. If both match, then the tool chain should be available when building with that Qt version.

        1 Reply Last reply Reply Quote 0
        • mzimmers
          mzimmers last edited by

          Thanks, Tobias -

          My issue seems to have self corrected since my original post. But the customer may well be having the same problem, so I'd better pursue this a little more. What does it mean if the ABIs don't match? It seems kind of weird that the MinGW supplied with Qt wouldn't work, too, but that's what the customer claims to have experienced.

          1 Reply Last reply Reply Quote 0
          • T
            tobias.hunger last edited by

            Depends... If your customer is using a Qt built with MSVC then it would not be surprising that he could not select a Mingw compiler. Hard to say whether or not there is an issue with some more information.

            1 Reply Last reply Reply Quote 0
            • mzimmers
              mzimmers last edited by

              I'm 99% sure he just downloaded the Windows binary. I'll double check today.

              I wonder if it had something to do with the name of the directory he installed it in...I sort of remember something about MinGW not liking directories with spaces in their names.

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