Details
-
Bug
-
Resolution: Out of scope
-
P4: Low
-
None
-
5.6.0 RC
-
None
-
OSX 10.10
Description
We build our application against self-build libraries of Qt with Jenkins. So every jenkins will extract a .tar.xz with all dependencies to have a clean environment.
To let the build find the extracted libraries we define those env variables. Qt is built with "-no-rpath"!
export DYLD_FALLBACK_FRAMEWORK_PATH=/Users/build/Jenkins/workspace/App/libs/qml/build/dist/lib
export DYLD_FALLBACK_LIBRARY_PATH=/Users/build/Jenkins/workspace/App/libs/qml/build/dist/lib
This worked without problems in Qt 5.5.0 and Qt 5.6.0-beta:
"otool -L" for QtNetwork:
QtNetwork.framework/Versions/5/QtNetwork (compatibility version 5.5.0, current version 5.5.0)
QtCore.framework/Versions/5/QtCore (compatibility version 5.5.0, current version 5.5.0)libssl.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
This is broken since Qt 5.6.0rc because libaries contains an absolute rpath now!
"otool -L" for QtNetwork:
/Users/build/Jenkins/workspace/Review_Libs_MacOS/build/dist/lib/QtNetwork.framework/Versions/5/QtNetwork (compatibility version 5.6.0, current version 5.6.0)
/Users/build/Jenkins/workspace/Review_Libs_MacOS/build/dist/lib/QtCore.framework/Versions/5/QtCore (compatibility version 5.6.0, current version 5.6.0)
libssl.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
Attachments
Issue Links
- is duplicated by
-
QTBUG-51403 [OS X]: Add a configure option to complement -no-rpath on OS X so that it is possible to turn off the absolute_library_soname option
- Closed
- resulted from
-
QTBUG-48958 [OS X]: When configuring Qt with -no-rpath then it fails to run any applications built against it
- Closed