When building Qt against homebrew provided 3rd party libs, so qtbase/configure -pkg-config, QtNetwork ends up depending on libbrotlidec.dylib. Thus, we get the following dependency chain: (1) QtNetwork.framework -> (2) libbrotlidec.dylib -> (3) libbrotlicommon.1.dylib In this case when an app links to QtNetwork and is deployed with macdeployqt, it would get the libbrotlidec.dylib copied into the app bundle Frameworks dir, but not libbrotlicommon.1.dylib. That happens because macdeployqt only considers the Qt prefix and the app bundle paths as rpaths when resolving @rpath dependencies of copied libbrotlidec.dylib library, thus skipping the libbrotlicommon.1.dylib library. Fix this by adding the rpaths of the library, resolved relative to its original source location to the candidate rpaths. Make sure to add these rpaths only once to avoid unnecessary duplicates. Pick-to: 6.10 6.11 Fixes: QTBUG-100686 Change-Id: I0aea9e185db3475b3fd280d5103e9b169a9c1afa Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>