To bundle a Mac OSX application dynamically linked with Qt, there is macdeployqt.
To finish the job there is macdeployqtfix...

• Find dependencies and rpaths of :
  • the main binary of the bundle (i.e your app)
  • the dependencies of your app, and their dependencies, and their... (you got it!)
  • the plugins present in the bundle
• Copy into the bundle the missing QT libs on which your app depends, that should normally have been taken care of by macdeployqt
• Fix incorrect permissions
• Fix incorrect rpaths

macdeployqtfix relies on otool and install_name_tool being on the PATH

❗ 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:

• your Qt application is named APP
• the bundle is located at /path/to/bundle/
• the path to those Qt libs used to build your app is /usr/local/Cellar/qt5/5.5.0/

1. Run macdeployqt first, as they say in the doc
2. Finish the job by calling:

python macdeployqtfix.py /path/to/bundle/Contents/MacOS/APP /usr/local/Cellar/qt5/5.5.0/