If your application includes QtWebEngine the macdeployqt application should also deploy QtWebEngineProcess and the support files needed. Currently this needs to be done manually.

FOR 5.4 YOU MUST RUN macdeployqt THE FOLLOWING WAY:

> macdeployqt <TARGET>.app -executable=<TARGET>.app/Contents/MacOS/<TARGET>

macdeployqt only uses @loader_path when the -executable switch is non-empty, so passing an arbitrary exectable there triggers the behavior we need to let QtWebEngineProcess use the same Qt binaries as the main application executable. The won't be necessary once we support using @rpath, which should be done in Qt 5.5.0.