[Interest] Qt 5.4.x QML Quick2 OSX STANDARD framework deployments

rpzrpzrpz at gmail.com rpzrpzrpz at gmail.com
Sun May 10 21:30:42 CEST 2015


Oliver:

I took your advice to heart.

I think there is a happy middle ground using scripts.

During in-house development, I can send everyone a given app with a 
fully self contained bundle.  Ultimately, this will satisfy store 
requirements.

But for in-house development, 2 script files can run macdeployqt, 
extract and compress the binary inside the testapp.app file, and place 
the smaller file onto the DropBox distribution directory for over the 
internet distribution.

On the user side, they can run a script to import the compressed binary 
into the proper testapp.app file on their local machine.

This will avoid the repeated download of the massive QT5 libraries and 
frameworks everytime we ship a new version of the application.

And it will not break the protocol of using self contained bundles for 
applications.

Cheers,

Mark



On 5/9/2015 1:26 AM, Till Oliver Knoll wrote:
>
>
>
>
>> Am 09.05.2015 um 03:01 schrieb mark diener <rpzrpzrpz at gmail.com>:
>>
>> Found a reference to the issue to install into /Library/Qt directory and install-name-tool :
>
> Just be aware that this is /very/ unusual for OS X apps to do: the expected way is really that each app bundle is self-contained and links against "system provided frameworks" (Cocoa and friends). Even if that means that each application brings along its own Qt libs...
>
> Needless to say that the former approach needs an "installer" (which is discouraged very much by Apple) and you run into issues when users want to get rid of one of your applications: "Who is the last to remove the shared Qt libraries"?
>
> And what happens if a user installs an older app, possibly overwriting a newer shared Qt library? Your installer needs to do a version check etc. to solve this.
>
> And it goes without saying that your applications will never make it into the Mac App Store that way - if that's what you want.
>
>
> On the other hand if we're talking about some "in-house tools" which are deployed in a controlled manner then this is a fine approach :)
>
> Just some thoughts...
>
> Cheers,
>    Oliver
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>

-- 
No spell checkers were harmed during the creation of this message.



More information about the Interest mailing list