Problem opening Qt5.5.1 app on OS X 10.6.8



  • I have an application developed with Qt 5.5.1 on a system running OS X 10.10.5. The application will not open for a user attempting to use it on OS X 10.6.8. The problem report states that "App cannot be opened because of a problem." I have deployed the application bundle on my system where it works fine. Are there issues with deploying to 10.6.8 (Snow Leopard)?


  • Moderators

    Usually on that "there is a problem" screen on osx, you can get more information. Which is basically like a crash log. Can you post that info here?

    Or barring that can you open the application in a debugger and show us the info from that?

    And final question, did you limit your target osx platform when you built? Something like:

    QMAKE_CFLAGS += -mmacosx-version-min=10.6
    QMAKE_CXXFLAGS += -mmacosx-version-min=10.6
    

    Or did you use something like:

    macx:QMAKE_MACOSX_DEPLOYMENT_TARGET = 10.6
    

    in your project file? ^ had to look that one up, I use cmake these days and couldn't remember the syntax.



  • 10.6 support was drop, I think Qt 5.3.2 is the last version to support it.


  • Lifetime Qt Champion

    10.6 was dropped as a build platform however applications should be able to run on it (provided that no API from newer version of OS X are used)



  • @SGaist said:

    ...(provided that no API from newer version of OS X are used)

    That's exactly what happen, newer API are now used unconditionally and 10.6 fallback has been removed.

    see:
    a198ce8d8fe9b418d631d033d481ec38f0373fa4
    fc11798e8f5997dd350a9baf39e9a3124b04fdd1
    9c92a18b975173383454c13d34f4438636f0450c
    etc

    That was for Qt5.4, so like I said, stick with Qt5.3.2 for 10.6 support.


  • Lifetime Qt Champion

    Fair enough, then the documentation is not reflecting that move.



  • I went back to version Qt5.3.2 and now the app developed with it on a recent OS X runs on OS X 10.6.8. Thanks for the advice.


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.