[Interest] Non-movable Qt build

Thiago Macieira thiago.macieira at intel.com
Wed Dec 26 21:28:23 CET 2012


On quarta-feira, 26 de dezembro de 2012 14.58.03, K. Frank wrote:
> First note, my experience is with older versions, not Qt 5.
> 
> As I understand it, it is not practical to move a Qt installation away
> from where it is built.
> 
> (There is supposedly some tool that you can use to rewrite the
> hard-coded paths embedded in the executables.  I'm don't know
> for sure whether such a tool exists, if it does, I'm not sure it works,
> and if it did work, it would still be an incredible hack.)
> 
> This has been stated to be by design, and a feature, not a bug.
> 
> This makes no sense to me of course.  I have had to rebuild Qt
> a couple of times in order to relocate an otherwise non-relocatable
> Qt installation (and the build process is slow).
> 
> Sure, it's okay to have hard-coded absolute paths in the executables,
> but they should be used only as a last resort, and should normally
> be superseded by a QT_HOME environment variable or the location
> of the executable being run or some other such trivially relocatable
> mechanism.
> 
> But, as I understand it, this battle has been fought already in the past,
> and, unfortunately, lost.
> 
> 
> Happy (Non-Relocatable) Hacking!

Note that there's a difference between running Qt-based applications (and 
that's what qt.conf is for) and the building of applications against a 
particular Qt build.

The former is relocatable by way of the config file. The latter is a different 
thing. It definitely isn't for Qt 5.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20121226/7812502c/attachment.sig>


More information about the Interest mailing list