why Qt designed to be unmoveable after installation?
-
I spend hours for successfully compile the static version of 5.8 last night. after move the binaries to new location, qtcreator complains that the qt is not properly installed and let me run make install.
Unfortunately, I deleted the source this morning, in this case, is there a easier way to solve this problem instead of rebuild everything?
Also, why it designed to be unmoveable after installation? what's the point to "hard code" the path into the qmake exe file?
Thanks.
-
Maybe this project will help you: QtBinPatcher.
-
I'm not 100% sure and don't have much time to check, but can't a qt.conf file help you?
See http://doc.qt.io/qt-5/qt-conf.html -
I spend hours for successfully compile the static version of 5.8 last night. after move the binaries to new location, qtcreator complains that the qt is not properly installed and let me run make install.
Unfortunately, I deleted the source this morning, in this case, is there a easier way to solve this problem instead of rebuild everything?
Also, why it designed to be unmoveable after installation? what's the point to "hard code" the path into the qmake exe file?
Thanks.
@Adam-BZH I move Qt after I build it all the time.
Assuming linux here, you can use chrpath to fix where the libs point, or you can just use a qt.conf file. On osx you can use otool to fix the libs.
Mostly I opt for the latter. Here is an example:
[Paths] Plugins = /path/to/qt/plugins
