[solved] macdeployqt...again

PSI-lbc

So I'm giving a newer version of Qt a trial run...MacOS V5.0.2...after having used V4.7.3 for quite a while.

The .pro file contains...

equals(QT_MAJOR_VERSION, 5) {
#5.0.2
QT += core gui
QT += declarative
QT += widgets
QT += webkit
QT += webkitwidgets
QT += printsupport
QT += xml
QT += network
}

Running macdeployqt inserts the following into the app bundle..

Framework...
QtCore
QtDeclarative
QtGui
QtNetwork
QtOpenGL
QtPrintSupport
QtQml
QtQuick
QtScript
QtSql
QtV8
QtWebKit
QtWebkitWidgets
QtWidgets
QtXml
QtXmlPatterns

Plugins…
accessible
imageformats
platforms
printsupport
sqldrivers

Is the version of "macdeployqt" shipped with MacOS V5.0.2 (Desktop_Qt_5_0_2_clang_64bit) "just not quite there"..ie a bit buggy ?

I'm pretty sure based on the .pro file inclusion list that I don't need...QtQml, QtQuick ,QtScript, QtSql, QtV8, QtOpenGL, or QtXmlPatterns in the Frameworks...and sqldrivers in the plugins.

Is there a secret to getting macdeployqt to work...or do you just run it to let it add the entire framework and plugin items to the app bundle then manually delete the items you think you don't need?

KeithS

macdeployqt is a little dumb in this area.

I have a script 'deploy' which basically does:

macdeployqt ./my.app
rm -rf ./my_app/Contents/Frameworks/QtNetwork.framework

etc...

rm -rf ./myApp/Contents/Plugins/accessible

etc...

It also goes into the Contents directory and edits the Info.plist to change 'yourcompany' to whatever name you want.

SGaist

Hi,

macdeployqt is in need of some attention and AFAIK should get some in the near future. In the meantime, you will have to handle some parts yourself. As KeithS wrote, a little script to either cleanup or do some missing updates is the best way to go.

PSI-lbc

Thx.

Kinda suspected as much. I have Apple Automater shell scripts that remove the unnecessary frameworks and plugins from the app bundle, but I thought there might be macdeployqt command line option I was missing.

SGaist

It should be handled correctly from the start (that's the idea behind qmacdeployqt)

The future might bring us some needed improvements in that area :)