Details
-
Suggestion
-
Resolution: Done
-
P2: Important
-
None
Description
Make it possible to move the Qt installation and libraries without breaking functionality or loading of plugins.
Attachments
Issue Links
- depends on
-
QTBUG-15234 Qt hard-codes paths in libraries/binaries
- Closed
-
QTBUG-31814 Qt 4.x and Qt 5 frameworks should use @rpath
- Closed
- is duplicated by
-
QTBUG-45875 LIBPATH is not correctly generated with changed location of Qt binaries.
- Closed
-
QTBUG-66347 qt.conf - isn't solving a major problem for developers!
- Closed
- is required for
-
QTBUG-40899 qmake create faulty Link->AdditionalDependencies entries in Visual Studio project file if we use the modules "axcontainer", "axserver" or "uitools" in *.pro file
- Closed
-
QTBUG-16208 Sign binary packages for Windows Vista/7
- Closed
- relates to
-
QTBUG-44473 KDE relies on QStandardPath for shared resource lookups, which fails when running on non Linux systems
- Withdrawn
-
QTBUG-29550 Can't set path to a platform plugin in a portable way
- Closed
-
QTBUG-38598 Calling QCoreApplication::libraryPaths Before Constructing QApplication Causes Platform Plugins to Fail to Load
- Closed
-
QTBUG-81612 Deployment doc still mentions hardcoded prefix path in Qt5Core.dll
- Closed
- replaces
-
QTBUG-28292 Qt doesn't work with long building path
- Closed