macdeployqt

macdeployqt not copying plugins

瘦欲@ — Fri, 24 Jan 2020 02:40:07 +0000

macdeployqt not copying plugins 瘦欲@ 2020-01-24 10:40:07

问题

I'm developing a Qt-based application and when I use macdeployqt on the bundle, the Qt plugins are not copied to the bundle.

However, if I run it a second time, they are. Additionally, "The svg icon plugin is deployed if the application uses the QtSvg module." is not fullfilled - my application does use QtSvg but the iconengines/* plugin is not copied.

I tried running it with -verbose=3, and the last couple lines are:

Log: Created configuration file: "silverlock.app/Contents/Resources/qt.conf" 
Log: This file sets the plugin search path to "silverlock.app/Contents/PlugIns"

From what the last message says, it kind of seems that it intended to continue running, but didn't - almost as if it crashed.

Why is this happening? macdeployqt has worked for me before without issue.

Using:

Qt 4.6
Qt Creator 2.0
Leopard 10.5.8

回答1:

The problem lies at lines 355-365 of shared.cpp in the macdeployqt source:

while (frameworks.isEmpty() == false) {
    const FrameworkInfo framework = frameworks.takeFirst();
    copiedFrameworks.append(framework.frameworkName);

    // Get the qt path from one of the Qt frameworks;
    if (deploymenInfo.qtPath.isNull() && framework.frameworkName.contains("Qt") 
        && framework.frameworkDirectory.contains("/lib"))
    {
            deploymenInfo.qtPath = framework.frameworkDirectory;
            deploymenInfo.qtPath.chop(5); // remove "/lib/"
    }

The first framework/dylib name in your bundle that has "Qt" in its name is taken to determine the plugin path. Since the first framework/dylib name in my bundle was "QtSolutions_QtSingleApplication-2.6"... you get the picture. So I suppose a workaround is to rename the dylib to "qsa-2.6.dylib" or something.

In a nutshell: make sure your framework and library names don't have "Qt" in them or you'll run into issues with macdeployqt.

Hopefully this answer may help someone having the same issue.

来源：https://stackoverflow.com/questions/3454001/macdeployqt-not-copying-plugins

标签

c++

macos

macdeployqt

macdeployqt and third party libraries

久未见 — Sun, 29 Dec 2019 06:58:26 +0000

macdeployqt and third party libraries 久未见 2019-12-29 14:58:26

问题

I've got an application project that depends on a couple of shared libraries that I have created myself. According to the Qt 4.6 documentation "Deploying an Application on Mac OSX":

Note: If you want a 3rd party library to be included in your application bundle, then you must add an excplicit lib entry for that library to your application's .pro file. Otherwise, the macdeployqt tool will not copy the 3rd party .dylib into the bundle.

I have added lib entries to my application's .pro file but the libraries that I have written do not get copied into the bundle when I execute macdeployqt. I have the following in my .pro file:

LIBS += -L../Libraries -lMyLib

Everything builds okay, its just when I try to run from the bundle that I run into problems i.e. "image not found" errors.

Is there a bug in macdeployqt or do I have to something more to my .pro file?

回答1:

badcat is correct that the Qt 4.6 documentation has a grossly inflated view of what is possible with macdeployqt tool.

In my experience, the only things that are done by macdeployqt are:

Copy the Qt libraries into your app bundle in the foo.app/Contents/Frameworks/ directory
Adjusts the link libraries of one binary, namely foo.app/Contents/MacOS/foo (must have same name as app bundle, even if you mention another binary in Info.plist)

So, for every other binary and library you want to deploy in your app bundle, you must do the following:

Run macdeployqt to enjoy its useful but feebly inadequate benefits

macdeployqt <path_to_your_nascent_app_bundle>/foo.app
Install your extra libraries manually

cp <original_library_path> foo.app/Contents/Frameworks/<lib_name>
Find out what libraries each binary links to.

otool -L <binary_file_name>
Change the internal libary paths in your binaries

install_name_tool -change <original_library_path> @executable_path/../Frameworks/<lib_name> <binary_file_name>

I wrote a perl script that automates these steps for my application, but it's a bit too specific to my particular environment to post here.

回答2:

You don't need to take care about manual deployment of third-party libraries. I am uploading a patch to Qt that makes it possible to specify additional library search paths, so that the macdeployqt tool finds the third-party dependencies: https://codereview.qt-project.org/#change,47906

After this one there will be another commit that will add support for third party libraries' deployment.

回答3:

Did you check the .app bundle to see if the libraries are really not there?

If that's the case, I'd assume there really is a bug in macdeployqt, or it simply can't find the library you are linking. Personally I've never seen macdeployqt actually copy any needed 3rd-party libraries into the bundle.

The interesting part is that macdeployqt never ever works directly with the .pro file. It just does some stuff to the produced application bundle. And after a quick glance into the documentation this Qt 4.7 documentation page obviously proves me right:

Note: If you want a 3rd party library to be included in your application bundle, then you must copy the library into the bundle manually, after the bundle is created.

I'd assume there is a bug in the 4.6 documentation. For me macdeployqt never placed any library files in my bundle (except for the Qt* ones, of course).

I did spend a lot of time with this stuff in my past, and ended up writing a simple little (Python) script that packs everything up into my bundle, changes the library names as needed and puts everything in a .dmg file with automatic naming.

Possibly not what you wanted to hear, but it works. ;)

回答4:

https://github.com/auriamg/macdylibbundler

dylibbundler is a small command-line programs that aims to make bundling .dylibs as easy as possible. It automatically determines which dylibs are needed by your program, copies these libraries inside the app bundle, and fixes both them and the executable to be ready for distribution... all this with a single command on the teminal! It will also work if your program uses plug-ins that have dependencies too.

来源：https://stackoverflow.com/questions/2809930/macdeployqt-and-third-party-libraries

标签

deployment

macdeployqt

Macdeployqt is not working

旧巷老猫 — Mon, 23 Dec 2019 17:25:52 +0000

Macdeployqt is not working 旧巷老猫 2019-12-24 01:25:52

问题

I've installed the latest version of Qt (5.1) and when I try to deploy my app on Mac using the macdeployqt tool, the app is still not working on other macs. It's completely working on my Mac and it doesn't not indicate any errors. After researches I found this and I think it's my problem : Qt 5.1 and Mac: Bug making macdeployqt not working properly and https://bugreports.qt-project.org/browse/QTBUG-14699 But the explanation is too technical for me (+ english not my native language), I'm a complete beginner, can you explain what do I have to do to simply make my app work on Mac ? Step by step ? It is perfectly functional on Windows (with the standard dlls).

Thank you so much, I think it will help a lot of beginners that are going through the same issue.

回答1:

There are 3 tools at your disposal to sort out deployment of Qt for OS X (MacOS).

macdeployqt: This tool gathers all the Qt libraries that your application declares it needs in its project, adds them to the app bundle and updates their paths so that your application knows where to find them.
otool: A complex tool for examining the contents of binaries, but in this case, used with the -L argument, will display the paths to all the libraries that your application will reference. These are the paths that it will be looking to find those libraries.
install_name_tool: Since macdeployqt only handles Qt libraries that are required by your application, you can use install_name_tool to update paths to any other libraries that your app requires. For example, if you have a separate non-Qt framework that your application relies upon, you need to have a post compilation step to copy the framework into the application bundle and then use install_name_tool to update the paths to the framework.

If you're having problems, check that the libraries / frameworks have been copied to the correct location in the application bundle and then use otool -L to check the paths. If any are incorrect, use name_install tool to fix them.

If you still can't get it to work, please edit your question and add the output from using otool -L.

Note, historically, various versions of Qt have suffered bugs with the macdeployqt utility, so if it is not working properly, you may also want to check the qt bug tracker.

来源：https://stackoverflow.com/questions/17957127/macdeployqt-is-not-working

标签

c++

macdeployqt

How do I make apps smaller with qmake and macdeployqt

￡可爱￡侵袭症＋ — Fri, 20 Dec 2019 20:49:19 +0000

How do I make apps smaller with qmake and macdeployqt ￡可爱￡侵袭症＋ 2019-12-21 04:49:19

问题

How do I make apps smaller with qmake and macdeployqt?

I have set QT = core gui in the projects .pro file and run qmake and macdeployqt on the resulting app.

The problem is that the program is bundling QtNetwork, QtScript, QtSvg etc. I've tried setting QT -= network script svg (and then make clean, rm -rf *.app, qmake, make).

In total the app is 32 MB.

.pro file:

TEMPLATE = app
TARGET = throw
DEPENDPATH += .
INCLUDEPATH += .
CONFIG += x86_64 release
QT = core gui

unix {
    CONFIG += link_pkgconfig
    PKGCONFIG += glib-2.0
}

# Input
SOURCES += main.cpp

# Headers
HEADERS += throw.h

RESOURCES += throw.qrc

ICON = throw.png

mac {
    QMAKE_INFO_PLIST = Info.plist
    ICON = throw.icns
}

回答1:

This is a great article about (re)building Qt statically and dynamically to reduce its size considerably: Building Qt Static (and Dynamic) and Making it Small with GCC, Microsoft Visual Studio, and the Intel Compiler

While this is talking about Qt in the windows context, it does give some good insight into how one would go about compiling for minimal size.

回答2:

You could strip the binary afterwards in a post-build step. The Qt libraries themselves are shared by default.

来源：https://stackoverflow.com/questions/6562725/how-do-i-make-apps-smaller-with-qmake-and-macdeployqt

标签

Qt 5.1 and Mac: Bug making macdeployqt not working properly

自闭症网瘾萝莉.ら — Tue, 17 Dec 2019 19:59:09 +0000

Qt 5.1 and Mac: Bug making macdeployqt not working properly 自闭症网瘾萝莉.ら 2019-12-18 03:59:09

问题

I have a problem since the version 5.1rc2 of Qt for Mac OS X. (5.1 is also affected, not the 5.1rc1)
When I build my app and do a otool -L on the binary file to see the paths of the shared libraries, I get: (it's just a sample, I removed some of them for clarity)

/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit 
    (compatibility version 45.0.0, current version 1187.37.0)
/Users/chris/**Qt5.1.0//5.1.0**/clang_64/lib/QtWebKitWidgets.framework/Versions/5/QtWebKitWidgets
    (compatibility version 5.1.0, current version 5.1.0)
/Users/chris/Qt5.1.0//5.1.0/clang_64/lib/QtQuick.framework/Versions/5/QtQuick
    (compatibility version 5.1.0, current version 5.1.0)
/Users/chris/Qt5.1.0//5.1.0/clang_64/lib/QtQml.framework/Versions/5/QtQml
    (compatibility version 5.1.0, current version 5.1.0)
/Users/chris/Qt5.1.0//5.1.0/clang_64/lib/QtNetwork.framework/Versions/5/QtNetwork
    (compatibility version 5.1.0, current version 5.1.0)
/Users/chris/Qt5.1.0//5.1.0/clang_64/lib/QtCore.framework/Versions/5/QtCore
    (compatibility version 5.1.0, current version 5.1.0)
/Users/chris/Qt5.1.0//5.1.0/clang_64/lib/QtGui.framework/Versions/5/QtGui
    (compatibility version 5.1.0, current version 5.1.0)

As you can see there is a double slash in the paths of the Qt libraries. When I use macdeployqt to deploy my app, those paths aren't changed to local frameworks (@executable_path/../Frameworks/...), because of this... I have to do it manually with the install_name_tool, and it's really annoying.

What can I do to fix this? (I've tried re-installing Qt, cleaning, runing qmake again and rebuilding without change)

回答1:

having the same issue. I applied next workaround:

after I build my program, I've changed links inside exe to a right ones

install_name_tool -change /Users/username/Qt5.1.0//5.1.0/clang_64/lib/QtQuick.framework/Versions/5/QtQuick  /Users/username/Qt5.1.0/5.1.0/clang_64/lib/QtQuick.framework/Versions/5/QtQuick <YourExecutable>

After this workaround macdeployqt has changed all links inside exe to a relative ones.

But my App became broken. The thing is that I've added all my images and QML files into resources. After I ran macdeployqt - I can not run my app. When I ran this with gdb - I see next error:

QQmlApplicationEngine failed to load component 
qrc:/qml/main.qml:-1 File not found

Error: Your root item has to be a Window.

So somehow all my resources became unavailable. Does anyone know how to fix that?

I also started a discussion on qt forum

UPDATE, HOW TO DEPLOY:

Use this script to get rid of double slashes inside dynamic linking paths.

./fixqt.sh ~/Qt5.1.0/5.1.0/clang_64
Build macdeployqt tool from this repository.
Run macdeployqt and specify dir with your qml source:

macdeployqt MyApp.app/ -qmldir=../src/qml -dmg

After those steps I managed to run my application on different OS X system, without QT Installed. I've added all my qml files and images into resources. QtQuick and QtQuick.2 modules copied inside MyApp.app/Content/MacOS/

Hope it helps

回答2:

I'm posting this as a solution as I just lost (another) day to this process with 5.3 (and I assume it is the same for 5.4).

macdeployqt now works as intended but the failed piece of documentation here is that you need to specify and absolute path to each qml directory (relative might work but I've had no luck at all).

Here's how I solved that for my release process:

In the project file I now have

  mac {
    CONFIG += x86
    CONFIG += c++11
    #Disable these for development
    QMAKE_MACOSX_DEPLOYMENT_TARGET = 10.9 #I'm not sure I need this
    QMAKE_POST_LINK = {path to macdeployqt}/macdeployqt {appname}.app -qmldir=$$PWD/qml/{appname}/ -verbose=3
  }

This effectively calls: macdeployqt appname.app - /path/to/source/code/appname/qml/appname/ -verbose=3

When the absolute path is specified it appears to work fine but when I use a relative path I run into several problems. PWD is the source directory and the executables are run from the build directory. The absolute path of the build is OUT_PWD.

The beauty of keeping this in the release configuration in the project is that I debug normally (no app package) and the release package correctly builds from creator. Theoretically I can just wrap that into a Jenkins build and be done with this headache once and for all.

The Short Answer

macdeployqt MUST SCAN your qml files if you're using them otherwise the imports will be broken and you'll see errors like:

QQmlApplicationEngine failed to load component
qrc:/qml/LightAssistant.qml:5 module "QtQuick.Dialogs" is not installed
qrc:/qml/LightAssistant.qml:3 module "QtQuick.Window" is not installed
qrc:/qml/LightAssistant.qml:4 module "QtQuick.Controls" is not installed
qrc:/qml/LightAssistant.qml:1 module "QtQuick" is not installed
qrc:/qml/LightAssistant.qml:2 module "QtQuick.Layouts" is not installed

Finally, my directory structure looks like this:

  Project
    - qml
      - appname
        files1.qml
        files2.qml
        ...
        filesX.qml 
    - js
    - images

These then get packaged into the Resource file which, by definition, are not copied to the build directory and thus macdeployqt can't scan them unless the pathing is perfect. By using this build process I have a step in my build (release) that just deals with it and I don't have to run macdeployqt when I'm debugging. Keep in mind if you use the app_bundle you need to run macdeployqt on each build which will really mess with your debugging workflow.

回答3:

This thread:

http://www.qtcentre.org/threads/55277-Qt-5-1-and-Mac-Bug-making-macdeployqt-not-working-properly

contains this link:

https://gist.github.com/lasconic/5965542

to this script by lasconic (not my work):

BIN_FILE=YOURBINARY
for P in `otool -L $BIN_FILE | awk '{print $1}'` 
do 
    if [[ "$P" == *//* ]] 
    then 
        PSLASH=$(echo $P | sed 's,//,/,g')
        install_name_tool -change $P $PSLASH $BIN_FILE
    fi 
done 

QTDIR=$1
for F in `find $QTDIR/lib $QTDIR/plugins $QTDIR/qml  -perm 755 -type f` 
do 
    for P in `otool -L $F | awk '{print $1}'`
    do   
        if [[ "$P" == *//* ]] 
        then 
            PSLASH=$(echo $P | sed 's,//,/,g')
            install_name_tool -change $P $PSLASH $F
        fi 
     done
done

You just need to replace YOURBINARY with e.g. myapp.app/Contents/MacOS/myapp

And QTDIR=$1 with QTDIR=/Users/MyName/Qt5.1.0/5.1.0/clang_64

Save the file in the same dir as myapp.app

And run it with

sh thankslasconic.sh

then you can run

macdeployqt myapp.app

and it should work. For me it did. That is why I am posting it here.

回答4:

I think its a installer bug. All librarys and tool (compiled/linked by installer?) referenced to .../Qt5.1.0//5.1.0/... (with double slash)

I've tried online and offline installer for Mac with the same result.

I've reported it as a bug. https://bugreports.qt-project.org/browse/QTBUG-32467

回答5:

Just as a follow-up, this bug appears to be fixed in Qt5.1.1 https://bugreports.qt.io/browse/QTBUG-32365

回答6:

Take a look at this site http://www.stringcat.com/company_blog/2013/07/04/failed-to-load-platform-cocoa/ See https://subversion.assembla.com/svn/blacktulipconfidence/branches/GuiDemoMac/ at the end of this page.

回答7:

Tried all of the above with qt 5.1.1 but always got this crash:

QMessageLogger::fatal(char const*, ...) const + 161
QGuiApplicationPrivate::createPlatformIntegration() + 1763
QGuiApplicationPrivate::createEventDispatcher() + 28
QCoreApplication::init() + 101
QCoreApplication::QCoreApplication(QCoreApplicationPrivate&) + 42

so I created this elixir, YMMV:

1) get the above mentioned mostly kinda working macqtdeploy from github.

2) build this new macqtdeploy

3) add this to main.cpp for mac os x only. this stuffs "-platformpluginpath" into argv before starting qapplication.

int macStart(int argc, char *argv[]) {
    QFileInfo fi(argv[0]);
    QDir plugd(fi.dir());
    plugd.cdUp();
    plugd.cd("PlugIns");
    QString plugins = plugd.absolutePath();
    qDebug() << "PlugIns" << plugins;

    char* argv_sub[argc + 2];
    for (int i = 0; i < argc; ++i) {
        char* temp = (char*) malloc(strlen(argv[i]) + 1);
        strcpy(temp, argv[i]);
        argv_sub[i] = temp;
    }

    char ppp[255];
    strcpy(ppp, "-platformpluginpath");
    argv_sub[argc] = ppp;

    char pathx[2048];
    strcpy(pathx, (char*) plugd.absolutePath().toLocal8Bit().constData());
    argv_sub[argc + 1] = pathx;

    DCApplication app(argc + 2, argv_sub);
    app.startup();
    return app.exec();
}

4) build app

5) run new macqtdeploy on app

6) goodness

回答8:

set plugin folder to libraryPaths

QStringList paths;
paths.append("folder with plugins"); //can be inside bundle
QApplication::setLibraryPaths(paths);

回答9:

I always ended up in this discussion when looking for a similar error with macdeployqt and QT Quick 2.0 using QML.

The error I found was this:

Machine:MacOS MyName$ ./tool QQmlApplicationEngine failed to load component qrc:/main.qml:1 plugin cannot be loaded for module "QtQuick": '/Users/thorstenbux/DAQRI/gitHub/artoolkit6/Source/Utilities/ImageDBSerialiser/build-ui/imageDatabase.app/Contents/PlugIns/quick/libqtquick2plugin.dylib' is not a valid Mach-O binary (not a dynamic library)

and this:

ERROR: Could not parse otool output: "/Users/myname/DAQRI/gitHub/tool/Source/Utilities/tool/build-tool-Desktop_Qt_5_8_0_clang_64bit-Release/tool.app/Contents/PlugIns/quick/libqtquick2plugin.dylib:\n"

I created a separate question for that kind of error here: QT Quick (QML) assemble mac-.bundle -> not a dynamic library error when using macdeployqt

Just in case someone has the same issue and reads this thread.

来源：https://stackoverflow.com/questions/17475788/qt-5-1-and-mac-bug-making-macdeployqt-not-working-properly

标签

macos

macdeployqt

How do I make apps smaller with qmake and macdeployqt

六眼飞鱼酱① — Tue, 03 Dec 2019 06:26:47 +0000

How do I make apps smaller with qmake and macdeployqt 六眼飞鱼酱① 2019-12-03 14:26:47

How do I make apps smaller with qmake and macdeployqt?

I have set QT = core gui in the projects .pro file and run qmake and macdeployqt on the resulting app.

The problem is that the program is bundling QtNetwork, QtScript, QtSvg etc. I've tried setting QT -= network script svg (and then make clean, rm -rf *.app, qmake, make).

In total the app is 32 MB.

.pro file:

TEMPLATE = app
TARGET = throw
DEPENDPATH += .
INCLUDEPATH += .
CONFIG += x86_64 release
QT = core gui

unix {
    CONFIG += link_pkgconfig
    PKGCONFIG += glib-2.0
}

# Input
SOURCES += main.cpp

# Headers
HEADERS += throw.h

RESOURCES += throw.qrc

ICON = throw.png

mac {
    QMAKE_INFO_PLIST = Info.plist
    ICON = throw.icns
}

While this is talking about Qt in the windows context, it does give some good insight into how one would go about compiling for minimal size.

You could strip the binary afterwards in a post-build step. The Qt libraries themselves are shared by default.

来源：https://stackoverflow.com/questions/6562725/how-do-i-make-apps-smaller-with-qmake-and-macdeployqt

标签

Qt 5.1 and Mac: Bug making macdeployqt not working properly

给你一囗甜甜゛ — Thu, 28 Nov 2019 19:38:15 +0000

Qt 5.1 and Mac: Bug making macdeployqt not working properly 给你一囗甜甜゛ 2019-11-29 03:38:15

/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit 
    (compatibility version 45.0.0, current version 1187.37.0)
/Users/chris/**Qt5.1.0//5.1.0**/clang_64/lib/QtWebKitWidgets.framework/Versions/5/QtWebKitWidgets
    (compatibility version 5.1.0, current version 5.1.0)
/Users/chris/Qt5.1.0//5.1.0/clang_64/lib/QtQuick.framework/Versions/5/QtQuick
    (compatibility version 5.1.0, current version 5.1.0)
/Users/chris/Qt5.1.0//5.1.0/clang_64/lib/QtQml.framework/Versions/5/QtQml
    (compatibility version 5.1.0, current version 5.1.0)
/Users/chris/Qt5.1.0//5.1.0/clang_64/lib/QtNetwork.framework/Versions/5/QtNetwork
    (compatibility version 5.1.0, current version 5.1.0)
/Users/chris/Qt5.1.0//5.1.0/clang_64/lib/QtCore.framework/Versions/5/QtCore
    (compatibility version 5.1.0, current version 5.1.0)
/Users/chris/Qt5.1.0//5.1.0/clang_64/lib/QtGui.framework/Versions/5/QtGui
    (compatibility version 5.1.0, current version 5.1.0)

What can I do to fix this? (I've tried re-installing Qt, cleaning, runing qmake again and rebuilding without change)

having the same issue. I applied next workaround:

after I build my program, I've changed links inside exe to a right ones

install_name_tool -change /Users/username/Qt5.1.0//5.1.0/clang_64/lib/QtQuick.framework/Versions/5/QtQuick  /Users/username/Qt5.1.0/5.1.0/clang_64/lib/QtQuick.framework/Versions/5/QtQuick <YourExecutable>

After this workaround macdeployqt has changed all links inside exe to a relative ones.

But my App became broken. The thing is that I've added all my images and QML files into resources. After I ran macdeployqt - I can not run my app. When I ran this with gdb - I see next error:

QQmlApplicationEngine failed to load component 
qrc:/qml/main.qml:-1 File not found

Error: Your root item has to be a Window.

So somehow all my resources became unavailable. Does anyone know how to fix that?

I also started a discussion on qt forum

UPDATE, HOW TO DEPLOY:

Use this script to get rid of double slashes inside dynamic linking paths.

./fixqt.sh ~/Qt5.1.0/5.1.0/clang_64
Build macdeployqt tool from this repository.
Run macdeployqt and specify dir with your qml source:

macdeployqt MyApp.app/ -qmldir=../src/qml -dmg

Hope it helps

I'm posting this as a solution as I just lost (another) day to this process with 5.3 (and I assume it is the same for 5.4).

Here's how I solved that for my release process:

In the project file I now have

  mac {
    CONFIG += x86
    CONFIG += c++11
    #Disable these for development
    QMAKE_MACOSX_DEPLOYMENT_TARGET = 10.9 #I'm not sure I need this
    QMAKE_POST_LINK = {path to macdeployqt}/macdeployqt {appname}.app -qmldir=$$PWD/qml/{appname}/ -verbose=3
  }

This effectively calls: macdeployqt appname.app - /path/to/source/code/appname/qml/appname/ -verbose=3

The Short Answer

macdeployqt MUST SCAN your qml files if you're using them otherwise the imports will be broken and you'll see errors like:

QQmlApplicationEngine failed to load component
qrc:/qml/LightAssistant.qml:5 module "QtQuick.Dialogs" is not installed
qrc:/qml/LightAssistant.qml:3 module "QtQuick.Window" is not installed
qrc:/qml/LightAssistant.qml:4 module "QtQuick.Controls" is not installed
qrc:/qml/LightAssistant.qml:1 module "QtQuick" is not installed
qrc:/qml/LightAssistant.qml:2 module "QtQuick.Layouts" is not installed

Finally, my directory structure looks like this:

  Project
    - qml
      - appname
        files1.qml
        files2.qml
        ...
        filesX.qml 
    - js
    - images

This thread:

http://www.qtcentre.org/threads/55277-Qt-5-1-and-Mac-Bug-making-macdeployqt-not-working-properly

contains this link:

https://gist.github.com/lasconic/5965542

to this script by lasconic (not my work):

BIN_FILE=YOURBINARY
for P in `otool -L $BIN_FILE | awk '{print $1}'` 
do 
    if [[ "$P" == *//* ]] 
    then 
        PSLASH=$(echo $P | sed 's,//,/,g')
        install_name_tool -change $P $PSLASH $BIN_FILE
    fi 
done 

QTDIR=$1
for F in `find $QTDIR/lib $QTDIR/plugins $QTDIR/qml  -perm 755 -type f` 
do 
    for P in `otool -L $F | awk '{print $1}'`
    do   
        if [[ "$P" == *//* ]] 
        then 
            PSLASH=$(echo $P | sed 's,//,/,g')
            install_name_tool -change $P $PSLASH $F
        fi 
     done
done

You just need to replace YOURBINARY with e.g. myapp.app/Contents/MacOS/myapp

And QTDIR=$1 with QTDIR=/Users/MyName/Qt5.1.0/5.1.0/clang_64

Save the file in the same dir as myapp.app

And run it with

sh thankslasconic.sh

then you can run

macdeployqt myapp.app

and it should work. For me it did. That is why I am posting it here.

I think its a installer bug. All librarys and tool (compiled/linked by installer?) referenced to .../Qt5.1.0//5.1.0/... (with double slash)

I've tried online and offline installer for Mac with the same result.

I've reported it as a bug. https://bugreports.qt-project.org/browse/QTBUG-32467

Just as a follow-up, this bug appears to be fixed in Qt5.1.1 https://bugreports.qt.io/browse/QTBUG-32365

Tried all of the above with qt 5.1.1 but always got this crash:

QMessageLogger::fatal(char const*, ...) const + 161
QGuiApplicationPrivate::createPlatformIntegration() + 1763
QGuiApplicationPrivate::createEventDispatcher() + 28
QCoreApplication::init() + 101
QCoreApplication::QCoreApplication(QCoreApplicationPrivate&) + 42

so I created this elixir, YMMV:

1) get the above mentioned mostly kinda working macqtdeploy from github.

2) build this new macqtdeploy

3) add this to main.cpp for mac os x only. this stuffs "-platformpluginpath" into argv before starting qapplication.

int macStart(int argc, char *argv[]) {
    QFileInfo fi(argv[0]);
    QDir plugd(fi.dir());
    plugd.cdUp();
    plugd.cd("PlugIns");
    QString plugins = plugd.absolutePath();
    qDebug() << "PlugIns" << plugins;

    char* argv_sub[argc + 2];
    for (int i = 0; i < argc; ++i) {
        char* temp = (char*) malloc(strlen(argv[i]) + 1);
        strcpy(temp, argv[i]);
        argv_sub[i] = temp;
    }

    char ppp[255];
    strcpy(ppp, "-platformpluginpath");
    argv_sub[argc] = ppp;

    char pathx[2048];
    strcpy(pathx, (char*) plugd.absolutePath().toLocal8Bit().constData());
    argv_sub[argc + 1] = pathx;

    DCApplication app(argc + 2, argv_sub);
    app.startup();
    return app.exec();
}

4) build app

5) run new macqtdeploy on app

6) goodness

set plugin folder to libraryPaths

QStringList paths;
paths.append("folder with plugins"); //can be inside bundle
QApplication::setLibraryPaths(paths);

Thor_Bux

I always ended up in this discussion when looking for a similar error with macdeployqt and QT Quick 2.0 using QML.

The error I found was this:

and this:

I created a separate question for that kind of error here: QT Quick (QML) assemble mac-.bundle -> not a dynamic library error when using macdeployqt

Just in case someone has the same issue and reads this thread.

来源：https://stackoverflow.com/questions/17475788/qt-5-1-and-mac-bug-making-macdeployqt-not-working-properly

标签

macos

macdeployqt