Deploying 3rdparty Qt Quick plugins on macOS
-
Thank you for your reply!
Unfortunately, macdeployqt does not seem to take QML2_IMPORT_PATH into account. I managed to make it find Kirigami by symlinking from inside Qt's qml folder to the library's location, but it feels hacky.
-
Hi,
There's the
-qmldiroption ofmacdeployqtthat you can use but AFAIK, it only takes one path currently. -
Thanks for the reply :)
According to the macdeployqt manual:
-qmldir=<path> : Scan for QML imports in the given path.This argument is used to specify the application's qml source directory to be scanned for
import *statements. It can accept multiple paths, but these are not used as library search paths.To specify a library search path, macdeployqt would need to pass it as an
-importPathargument to qmlimportscanner, but it only passes Qt's default library location: http://code.qt.io/cgit/qt/qttools.git/tree/src/macdeployqt/shared/shared.cpp#n1236As a hack one can create a link to the custom location from inside the Qt installation, and that's what I use for now, but I think there has to be a better way.
-
A feature to add to
macdeployqt: an option to give additional import paths. -
Should I open a feature request?
-
If you don't find any yet, yes. If you can provide a minimal buildable sample application that shows that behaviour it would be great.
Out of curiosity, how did you got Kirigami for macOS ?
-
@SGaist I reported the issue as https://bugreports.qt.io/browse/QTBUG-70977 and opened a revision at https://codereview.qt-project.org/#/c/242083/
-
Kirigami works just right on macOS, here are some screenshots:
The app is on its early stages, though.
-
Thanks for the submission !
One small fix to the commit message to do :)
-
Starting from Qt 5.13, there will be a
-qmlimportmacdeployqt option to specify additional QML module search directories. -
If needed earlier,
macdeployqtcan be manually built from the dev branch.
