[Interest] Deploying Qt to MacOs still...errr, sucks?

[Jean-Michaël Celerier]

Late bump :

The documentation is still lacking.
For instance, where should one deploy QtQuick's QML files ?

Upon inspection it seems that some plug-ins are put in
Contents/PlugIns/quick, some QML files in Resources/qml (similarly to
what's in Qt/5.$version/$platform/qml folder) and symlinks in
Resources/qml/QtQuick (or others) to the actual qml plug-ins.

Is all of this necessary ?

Best,
Jean-Michaël



-------
Jean-Michaël Celerier
http://www.jcelerier.name

On Thu, Feb 12, 2015 at 4:17 AM, Hamish Moffatt <hamish at risingsoftware.com>
wrote:

> On 12/02/15 05:11, Adam Light wrote:
> >
> > If you're using Qt 5 (maybe only 5.4), macdeployqt may be able to help
> > with the code signing and possibly the dmg part:
> >
> > /qtbuild5/install/mac64/bin/macdeployqt --help
>
> Unfortunately that's not much use if you need to do anything more than
> copy in Qt; for example bundle extra frameworks you are using, or remove
> Qt plugins you don't need. If you do either of those then you need to
> sign the app in your own scripts, because those operations will
> invalidate any signing done by macdeployqt.
>
> Of course macdeployqt could help by 1. supporting bundling other
> frameworks (which it can find via otool, as it does to find which Qt
> frameworks to bundle), and 2. allow you to include/exclude various Qt
> plugins.
>
> Right now it seems to bundle every plugin (or none, if you tell it to),
> which is both a waste of space and a no-go with the Mac App store for us.
>
>
> Hamish
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20161110/ac4c69b1/attachment.html>