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. macOS: CommandLineTools and mkspec mismatch
QtWS25 Last Chance

macOS: CommandLineTools and mkspec mismatch

Scheduled Pinned Locked Moved Unsolved Installation and Deployment
4 Posts 2 Posters 610 Views
  • 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.
  • J.HilkJ Offline
    J.HilkJ Offline
    J.Hilk
    Moderators
    wrote on last edited by
    #1

    Hi everyone,

    I recently setup a new MacOS dev environment, the previous hardware was not compatible with the newest OS, and I've run in a so far unencountered issue.

    I installed X-Code and Homebrew and during both installations Developer CommandLineTools where installed. And they are now duplicated on my System.

    As a result, the autodetection of the ios-Kit did not work. So I added it manually.
    QtCreator now tells me that qmake uses a different toolset than selected in the kits.

    in principle this shouldn't be an issue, and for desktop compilations it actually isn't, but when set to iOS I get the error "Could not recolve SDK Path for iPhones using --show-sdk-path"

    I would like to set the default toolset to the one installed by X-Code and as a result let the Auto-Kit detection do its magic. This should solve the warnings and the sdk-path issue as well.

    But I'm unsure how and where to do this.

    Greetings.


    Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


    Q: What's that?
    A: It's blue light.
    Q: What does it do?
    A: It turns blue.

    1 Reply Last reply
    0
    • J.HilkJ Offline
      J.HilkJ Offline
      J.Hilk
      Moderators
      wrote on last edited by
      #2

      Removing Homebrew solved the issue.

      My problem is gone, but if anyone has answer to the above question, I would like to hear/read it.


      Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


      Q: What's that?
      A: It's blue light.
      Q: What does it do?
      A: It turns blue.

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

        Hi,

        Any chance that the homebrew Qt qmake was in your PATH ?

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

        J.HilkJ 1 Reply Last reply
        0
        • SGaistS SGaist

          Hi,

          Any chance that the homebrew Qt qmake was in your PATH ?

          J.HilkJ Offline
          J.HilkJ Offline
          J.Hilk
          Moderators
          wrote on last edited by
          #4

          @SGaist hi,

          Chances are that Homebrew installation did make changes to the path. It does requier a sudo call to install correctly.

          Also after removing Homebrew, everything wan't fixed from the get go, I had to call sudo /usr/bin/xcode-select -switch /Applications/Xcode.app/Contents/Developer to fix compiler link errors.


          Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct


          Q: What's that?
          A: It's blue light.
          Q: What does it do?
          A: It turns blue.

          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