[Interest] Non-movable Qt build

[Yves Bailly]

Le 26/12/2012 21:28, Thiago Macieira a écrit :
> On quarta-feira, 26 de dezembro de 2012 14.58.03, K. Frank wrote:
>> As I understand it, it is not practical to move a Qt installation away
>> from where it is built.
>> [...]
>> But, as I understand it, this battle has been fought already in the past,
>> and, unfortunately, lost.

*sigh*

> 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.

My problem is precisely to build an application against a Qt build that has
been moved.

Just for the record, after changing hard-coded paths in the qt_*.pri files,
I managed to compile QtCreator 2.6.1 against my "relocated" Qt build. An
additional "qt.conf" is needed in QtCreator's "bin" directory, but it starts.

So, *if* it's enough to change the paths in the qt_*.pri files, it seems
we're not far from a relocatable Qt... "just" use relative paths in those files
instead of absolute ones, or use some variable like good'old QTDIR. Yes, I know
this "just" may well not be that simple.

Working in a team, until now I'm *THE* one building Qt from sources, then
everyone else just pick the binaries I provide in a kind of package. So
being able to move Qt around is quite important to us, having everyone
spending 4 hours rebuilding the same thing over and over is overkill.

The lost battles are the most delightful to restart... ;-)

Regards,

-- 
      /- Yves Bailly - Software developper  -\
      \- Sescoi R&D  - http://www.sescoi.fr -/
"The possible is done. The impossible is being done. For miracles,
thanks to allow a little delay."