QT 5.1 Deployment on mac OS X, macdeployqt does not change a links to qt libs inside application



  • Take a look on this link(on the last answer of stackOverflow)
    "deploy Qt5 apps to mac":http://www.stringcat.com/company_blog/2013/07/04/failed-to-load-platform-cocoa/

    Pretty complicated procedures, I am very new to mac and very surprise
    that deploy third parties dylib on mac could be so complicated, do anyone
    know what kind of benefits or reasons let mac os become so hard to
    deploy 3rd parties dll?Deal with those dependencies make me frustration.



  • I am sure the QtQuick Frameworks already copied to the bundle
    But the program can't find any components related to QtQuick control
    QtQuick control is under another module?

    Ah, find out the problem, the QtQuick control, layout and dialog are plugins under other folders

    The script do change the path of qml folder
    @for F in find $QTDIR/lib $QTDIR/plugins $QTDIR/qml -perm 755 -type f @
    But the macdeploy do not copy and configure the id and change the reference path of the dll
    I guess that despite of the bug, macdeploy do not support QtQuick control and QtQuick dialog yet
    or this is another bug of Qt5.1?



  • As far as I can see - it does not. Currently I'm struggling with QtQuick deployment. I got an error -

    @module "QtQuick" is not installed@

    I copied QtQuick and QtQuick.2 folders to app bundle, and added path to it, by using AddImportPath function inside my code. But anyway - it is not flying at the moment :/



  • [quote author="miks131" date="1373878229"]As far as I can see - it does not. Currently I'm struggling with QtQuick deployment. I got an error -

    @module "QtQuick" is not installed@

    I copied QtQuick and QtQuick.2 folders to app bundle, and added path to it, by using AddImportPath function inside my code. But anyway - it is not flying at the moment :/ [/quote]

    I have the same problem too, and I also copy the QtQuick.2 folders and
    part of the QtQuick folders to app bundle.Can't find a single success
    example of deploying QtQuick2 apps on mac.



  • Yep, another thread with the same "discussion ":http://qt-project.org/forums/viewthread/25903/



  • Finally managed to get it work, checkout this "answer":http://stackoverflow.com/a/17591828/2370437



  • miks131, thanks for your answer, thanks for macdeploy of MaximAlien, and the script from lasconic, they work like magic.
    Have you add you answer to the bug report you mention before?

    Hope your answer could help the developers solve this annoying bug, never
    though that deploy a simple app on mac is so painful, it is a real pain without
    the help of macdeployqt.

    After peeking into the bundle, I find out the folder of QtQuick.2 is place
    at the same folder as the exe, maybe this is why the project can't find
    the dylib before, because I put all of the plugins into the PlugIns folder



  • The important think here is that a solution MUST be included in a next version of Qt SDK as soon as possible! Until then, I will stick to Qt 4.8.5, and I would guess that I will not be the only one! ;-)



  • @steriomatching, just added answer to the bug report



  • Thanks, miks131

    I try your solution on a bigger project, the macdeployqt of MaximAlien provided do not
    copy the QtQuick folder into the bundle.Any possible reason would
    stop it copy the QtQuick folder into the bundle?

    I find out it is related to the qmldir, what is the correct way to set it?

    My folder layout

    "layout":http://www.flickr.com/photos/92283971@N04/9292932353/



  • how did you run it? Did you specify -qmldir=<path_to_your_qml> flag?



  • I specify it like this

    @macdeployqt.app/Contents/MacOS/macdeployqt/
    /Users/Qt/program/experiment_apps_and_libs/qmlTest2/qmlTest2.app/
    -qmldir=/Users/Qt/program/experiment_apps_and_libs/qmlTest2/qml/colorCorrection/
    -verbose=3@

    I update the layout of my folder on my previous post



  • bq. I will stick to Qt 4.8.5, and I would guess that I will not be the only one! ;-)

    I have the same opinion as yours, using Qt5.1 and QtQuick2 on a fun project, I would not recommend my colleague to pick Qt5.1 before it is stable enough.



  • Well, I can see only one reason - qml files inside colorCorrection folder does not have any import statements, or it is empty.

    Can't guess other reason.

    I dont think that size of project matters, I have quite a few files inside qml dir, and it works fine for me.



  • I find out the reason, I load an old shell, that is why the deployment always fail.Thanks for your helps and deeply hope this bug could be fixed on the next version(5.1.1), deal with the dependencies of Qt on mac is a real pain.

    Anybody know why the mac os make 99% of the dylib come with absolute path?



  • is there a fix for this that will come for Qt5.1.1 ? it seems a verious serious issue for using Qt on Mac ?



  • I just started looking at Mac deployment and am a bit confused about how hard it seems to be. I am not even a Mac user so might have missed or not understood things.

    I tried using the macdeployqt tool but it seems to leave a lot of work for the developer (modifying the paths, etc), if I understood what's written above, this is a bug in Qt 5.1 and will be corrected soon, right? I don't see any recent work on "git":https://qt.gitorious.org/qt/qttools/trees/stable/src/macdeployqt , does the tool need some love/contribution?

    I was wondering as well why the dylibs are burried deep inside Frameworks/QtX.framework/Versions/5/QtX and not directly copied in a Libraries directory in the root of the bundle (aside the MacOS folder)? Having this long path is a bit annoying when you have to manually fix the paths with install_name_tools. Is there a particular reason to have all this hierarchical directories? Aren't Frameworks for developers, containing the headers as well?



  • some news about this issue in the post on the Qt dev mailing list with thread
    "
    [Development] Puzzled by desktop development priorities, Mac OS specifically "



  • I'm using Qt 5.1.1, and deploying to OSX, but I am still getting errors similar to these.
    Specifically the qml imports:

    QQmlApplicationEngine failed to load component
    module "QtQuick.LocalStorage" is not installed
    module "QtQuick.Layouts" is not installed
    module "QtQuick.Controls" is not installed
    module "QtQuick" is not installed
    module "QtQuick.Dialogs" is not installed
    module "QtQuick.Controls.Styles" is not installed

    I'm using qtcreator & macdeployqt, but there is not a -qml option. Most sources say the macdeployqt command just works now in 5.1.1, but that still does not seem to be the case with qml. After all the debugging in this thread what is the canonical way to deploy to mac now?

    Thanks



  • [quote author="MrJoshua" date="1383605264"]I'm using Qt 5.1.1, and deploying to OSX, but I am still getting errors similar to these.
    Specifically the qml imports:

    QQmlApplicationEngine failed to load component
    module "QtQuick.LocalStorage" is not installed
    module "QtQuick.Layouts" is not installed
    module "QtQuick.Controls" is not installed
    module "QtQuick" is not installed
    module "QtQuick.Dialogs" is not installed
    module "QtQuick.Controls.Styles" is not installed

    I'm using qtcreator & macdeployqt, but there is not a -qml option. Most sources say the macdeployqt command just works now in 5.1.1, but that still does not seem to be the case with qml. After all the debugging in this thread what is the canonical way to deploy to mac now?

    Thanks[/quote]

    Yep. And also on 5.2.0 beta1 and rc1 (26.11.) snapshot.

    I'm using QtQuick2ApplicationViewer.



  • I believe this is fixed in the qt 5.2rc. You need to tell macdeployqt where your qml files are using -qmldir= (I believe it isn't recursive, so specify multiple times if you have multiple directories).



  • [quote author="jogu" date="1385661621"]I believe this is fixed in the qt 5.2rc. You need to tell macdeployqt where your qml files are using -qmldir= (I believe it isn't recursive, so specify multiple times if you have multiple directories).[/quote]
    Thanks! You saved my life :) Using -qmldir=/full/path/to/qmldir works.

    Update:
    Maybe someone will also need that. It's possible to create a deployment shortcut using Tools->External->Configure. Add new and in Executable locate macdeployqt app. In arguments insert @%{CurrentProject:BuildPath}/%{CurrentProject:Name}.app -qmldir=%{CurrentProject:Path}/qml/%{CurrentProject:Name}@
    It's faster and much easier with that :)



  • Would like to back up jogu's response: in 5.2rc this seems to be working correctly -- I've managed to use macdeployqt on several projects, and they all run when copied to a Mac with no Qt installed


Log in to reply
 

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