[Development] Relocating a Qt compilation

[Mark De Wit]

A qt.conf file could also help point to correct locations.   It doesn't have to be absolute, it can be relative?  This is how we deal with the hard-coded paths.

Mark

-----Original Message-----
From: Development <development-bounces+mark.dewit=iesve.com at qt-project.org> On Behalf Of Thiago Macieira
Sent: 28 June 2018 15:58
To: development at qt-project.org
Subject: Re: [Development] Relocating a Qt compilation

On Thursday, 28 June 2018 07:44:41 PDT Eric Lemanisser wrote:
> Hello,
> 
> I'm currently working on a Qt package for conan, and the fact that qt 
> files have absolute path hard-coded in them is problematic. The use 
> case is the following : a user downloads a binary distribution of Qt 
> (qmake+moc+include+libs etc.), which is then stored in a directory 
> which cannot be known when compiling said distribution.
> MaintenanceTool does the exact same job of downloading existing 
> binaries and storing them in directory chosen by the user, so it has 
> to patch the files. Are MaintenceTool's sources available, or at least 
> the patching process ? There used to be a small tool (qpatch? 
> qtpatch?) doing that, but I cannot find it

For a single-use build, you don't need to do that. Everything that needs to be found at runtime which would use those hardcoded paths can also be overridden by environment variables (XDG_CONFIG_DIRS, QT_PLUGIN_PATH and QML2_IMPORT_PATH).

--
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center



_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development