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. qmake error: Project ERROR: failed to parse default search paths from compiler output on MacOS High Sierra
Forum Updated to NodeBB v4.3 + New Features

qmake error: Project ERROR: failed to parse default search paths from compiler output on MacOS High Sierra

Scheduled Pinned Locked Moved Solved Installation and Deployment
3 Posts 3 Posters 7.1k Views 2 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
    hvoigt
    wrote on 29 May 2018, 13:11 last edited by hvoigt
    #1

    I just encountered the same problem like here: Can't get qmake to work from command line on MacOS High Sierra

    It seems that clang on High Sierra got a bit more picky when it comes to paths from environment variables.

    I had something like this in my .profile:

    export LD_PATH="$LD_PATH:$HOME/.local/lib"
    

    But LD_PATH was empty before this line, so the content had a colon in the beginning. E.g. like this:

    :/Users/hvoigt/.local/lib
    

    That lead to the error. Removing the colon or the content made qmake work again.

    I would blame this on OSX High Sierra, because I upgraded a machine to it which had a previous Qt installation lying around which worked fine before the upgrade.

    I thought I might put this solution out there, so others do not need to use as much time to solve this as I did.

    1 Reply Last reply
    2
    • E Offline
      E Offline
      et__
      wrote on 5 Dec 2020, 09:28 last edited by
      #2

      For others a similar problem on MacOS 10.15:

      "Project ERROR: failed to parse default search paths from compiler output"

      Issue was also similar - instead the shell variable 'LIBRARY_PATH' also somehow started with a colon. Fixed this and it also was resolved.

      1 Reply Last reply
      1
      • S Offline
        S Offline
        SGaist
        Lifetime Qt Champion
        wrote on 5 Dec 2020, 19:50 last edited by
        #3

        Hi,

        Usually when adding something to these variables, they are prepended because the goal is to make the newly added path(s) take precedence over the original list.

        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

        • Login

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