It looks like at least some fixes were included, as I'm able to build with
Qt 5.13.1 now (which was impossible with Qt Creator 4.10.0). But I've got
no idea exactly which commits were included either. Maybe it's just the
version bump commit that is missing?
Ola
tir. 8. okt. 2019 kl. 21:39 skrev
Hi guys,
Seems, you are forgot to deliver QBS 1.14.1 with QtC 4.10.1. Right now I
see that it use QBS 1.14.0.
How it happens? I was hoping for QBS 1.14.1... All my fixes go to
/dev/ass :((
BR,
Denis
___
Qbs mailing list
Qbs@qt-project.org
Am 08.10.19 um 12:00 schrieb Christian Kandeler:
> On Tue, 8 Oct 2019 11:39:09 +0200
> Heiko Nardmann wrote:
>
>> The question is whether to include Qt.core.libPath (as defined inside
>> core.qbs) into the list of rpaths. If I put it into the list then it
>> also is part of the binaries RPATH -
Am 08.10.19 um 10:51 schrieb Christian Kandeler:
> On Tue, 8 Oct 2019 09:53:32 +0200
> Heiko Nardmann wrote:
>
>> I'm looking for a way to prevent the RPATH of an executable pointing to
>> the installed Qt. From the "core.qbs" file I see that cpp.rpaths is set
>> to libPath for Linux by default.
Hi together,
I'm looking for a way to prevent the RPATH of an executable pointing to
the installed Qt. From the "core.qbs" file I see that cpp.rpaths is set
to libPath for Linux by default.
So ... do I have to change this file "core.qbs"??? The RPATH shall point
to the Qt that I deploy together
