[Development] Qt 5 packaging and binary renaming

Timo Jyrinki timo.jyrinki at gmail.com
Fri Dec 14 14:27:23 CET 2012

2012/12/13 Stephen Kelly <stephen.kelly at kdab.com>:
>> I'd simply go for putting the binaries into a separate directory as
>> discussed. The only side effect is that developers using Qt 5.0 will need
>> to adjust their path to get qmake from Qt 5. Once the chooser is available
>> that problem will solve itself.
> And if you set that path using the configure switch for it (-bindir?), the
> CMake files should be generated with the correct paths already without
> patching. That is why I ask how you set the location of the mkspec files - If
> you use the configure switch there should be no problems and no patch needed.

-archdatadir "/usr/share/qt5" is in use, which successfully changed
the target directory of the mkspecs files. So the binary renaming was
done by manually patching .prf and .pro files (qtPrepareTool and
TARGET), similar to current Qt4 in Debian, but mkspecs locations were
handled by Qt itself via the configure switches.

So next up would be using the bindir to install the binaries to a
version specific libexec directory instead.


More information about the Development mailing list