Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Language Bindings
  4. PySide 1.2.2 fails to build on Qt4 (Framework), OSX 10.9.4

PySide 1.2.2 fails to build on Qt4 (Framework), OSX 10.9.4

Scheduled Pinned Locked Moved Language Bindings
2 Posts 1 Posters 1.1k 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.
  • S Offline
    S Offline
    symbolix
    wrote on last edited by
    #1

    Hi,

    I have issues while building PySide on a system with Qt4 installed as a framework. I had Qt4.8.5 compiled from source and everything was under one single folder, ./bin ./include etc. Compiling PySide against that structure works just fine.

    However, recently I have installed Qt4.8.6 as a standard framework package. Obviously this means that things are under a framework folder hierarchy. So now, when I attempt to compile PySide against that Qt, it fails trying to find the header files.

    Any solutions?

    My Qt projects compile just fine, meaning, qmake finds the include files as frameworks. But CMake seems to fail as I described above. I have created a symlink for the first failing header:

    @~/myApps/Qt4.8.6/include/QtDesigner -> /Library/Frameworks/QtDesigner.framework/Headers@

    and this seems to be fixing the issue, so before going and creating a symbolic link for each header, I would like to ask if there is a more elegant solution.

    Thanks,
    Milen

    1 Reply Last reply
    0
    • S Offline
      S Offline
      symbolix
      wrote on last edited by
      #2

      Hi,

      Just an update, I wrote a quick bash script that created symbolic links for each:

      @/Library/Frameworks/Qt<module>.framework/Headers@

      folder in a custom location:

      @/myApps/Qt-4.8.6/include@

      And PySide compiled fine with CMake. Well, I have provided that path using the

      @-DALTERNATIVE_QT_INCLUDE_DIR@

      flag.

      However still curios to hear about this? How is that the CMake for PySide is not able to work with the framework based Qt?

      Thanks.

      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