That would be nice, but I doubt it is easy, since the deploy script need to figure out the Qml dependencies, so you need to give him the stating point to find the starting point to find .qml file. The .qrc is only a resources that package binary. It would be nice if the deploy script would scan the .qrc and auto add all the Qml files(--autoQrcQml flag). That would be a preprocessing that would scan the qrc and invoke the command again with the filled --qmldir or --qml. That would be fairly easy to even make such a script that would inject those before calling the windeployqt.
+1 on the auto scan of .qrc -----Original Message----- From: Interest <interest-boun...@qt-project.org> On Behalf Of Jason H Sent: December 4, 2019 11:47 AM To: "Roman Wüger" <roman.wue...@gmx.at> Cc: interestqt-project.org <interest@qt-project.org> Subject: Re: [Interest] windeployqt > Sent: Wednesday, November 27, 2019 at 2:16 PM > From: "Roman Wüger" <roman.wue...@gmx.at> > To: "Jason H" <jh...@gmx.com> > Cc: "interestqt-project.org" <interest@qt-project.org> > Subject: Re: [Interest] windeployqt > > Hello, > > try running windeployqt with the -qml or -qmldir option. Works for me. > > You must pass the qml directory to the Option like %QTDIR%\qml This seems redundandt. If all of my QML is in a qml.qrc, and that qrc is part of the project, shouldn't that "just work" without -qmldir ? _______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest _______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
