To bundle a Qt application on Mac OSX, there is macdeployqt. To finish the job there is macdeployqtfix! :white_check_mark:
To bundle a Mac OSX application dynamically linked with Qt, there is
macdeployqt
.
To finish the job there is macdeployqtfix
...
macdeployqtfix
relies on otool
and install_name_tool
being on the PATH
:exclamation: Use macdeployqt
first, then call macdeployqtfix
$ python macdeployqtfix.py -h
usage: macdeployqtfix.py [-h] [-q] [-nl] [-v] exepath qtpath
finish the job started by macdeployqt!
- find dependencies/rpaths with otool
- copy missed dependencies with cp and mkdir
- fix missed rpaths with install_name_tool
exit codes:
- 0 : success
- 1 : error
positional arguments:
exepath path to the binary depending on Qt
qtpath path of Qt libraries used to build the Qt application
optional arguments:
-h, --help show this help message and exit
-q, --quiet do not create log on standard output
-nl, --no-log-file do not create log file './macdeployqtfix.log'
-v, --verbose produce more log messages(debug log)
Let's say that:
APP
/path/to/bundle/
/usr/local/Cellar/qt5/5.5.0/
macdeployqt
first, as they say in the doc
python macdeployqtfix.py /path/to/bundle/Contents/MacOS/APP /usr/local/Cellar/qt5/5.5.0/