> -Original Message-
> From: Development On Behalf Of
> Thiago Macieira
> Sent: Tuesday, January 14, 2020 4:33 PM
> To: development@qt-project.org
> Subject: Re: [Development] Qt 5.14 MinGW debug build doesn't add debug
> suffix
>
> On Tuesday, 14 Jan
On Tuesday, 14 January 2020 00:02:01 PST Kai Köhne wrote:
> -debug-and-release was completely disabled in Qt 5.14.0, but will work again
> in Qt 5.14.1 (though still not be the default).
How will that work? Will it create debug libraries with different names
compared to a pure debug build?
BTW,
46 AM
> >> To: Thiago Macieira
> >> Cc: Qt development mailing list
> >> Subject: Re: [Development] Qt 5.14 MinGW debug build doesn't add debug
> suffix
> >>
> >> I've just discovered another side-effect of this change. I've
>
ieira
> > Cc: Qt development mailing list
> > Subject: Re: [Development] Qt 5.14 MinGW debug build doesn't add debug
> suffix
> >
> > I've just discovered another side-effect of this change. I've integrated
> the qdoc.exe in a custom toolchain for int
On 2020-01-14 09:02, Kai Köhne wrote:
From: Development On Behalf Of Dmitriy
Purgin
Sent: Tuesday, January 14, 2020 8:46 AM
To: Thiago Macieira
Cc: Qt development mailing list
Subject: Re: [Development] Qt 5.14 MinGW debug build doesn't add debug suffix
I've just discovered an
> From: Development On Behalf Of Dmitriy
> Purgin
> Sent: Tuesday, January 14, 2020 8:46 AM
> To: Thiago Macieira
> Cc: Qt development mailing list
> Subject: Re: [Development] Qt 5.14 MinGW debug build doesn't add debug suffix
>
> I've just discovered anothe
I've just discovered another side-effect of this change. I've integrated
the qdoc.exe in a custom toolchain for internal use, and it should be able
to run in environments without any Qt installations. So I used to do the
windeployqt.exe on it, and it always worked until 5.14. Now windeployqt
says t
Am Fr., 10. Jan. 2020 um 09:40 Uhr schrieb Roland Winklmeier <
roland.m.winklme...@gmail.com>:
> Am Mi., 8. Jan. 2020 um 20:09 Uhr schrieb Thiago Macieira <
> thiago.macie...@intel.com>:
>
>> On Wednesday, 8 January 2020 10:10:06 PST Sérgio Martins via Development
>> wrote:
>> > Wondering if there
Am Mi., 8. Jan. 2020 um 20:09 Uhr schrieb Thiago Macieira <
thiago.macie...@intel.com>:
> On Wednesday, 8 January 2020 10:10:06 PST Sérgio Martins via Development
> wrote:
> > Wondering if there's a reason why the suffix is needed in the first
> > place...
> > I thought only MSVC had problems mixi
On Wednesday, 8 January 2020 10:10:06 PST Sérgio Martins via Development
wrote:
> Wondering if there's a reason why the suffix is needed in the first
> place...
> I thought only MSVC had problems mixing debug and release runtimes.
Correct.
We stopped adding the suffix in MinGW builds.
I wonder
On 2020-01-07 12:52, Roland Winklmeier wrote:
Second, I switched my nightly build to 5.14 branch and was building
debug
binaries as usual. Configure arguments:
configureArguments=-developer-build -debug -opensource -nomake examples
-nomake tests -confirm-license -opengl desktop -dbus -openssl -
Am Di., 7. Jan. 2020 um 13:52 Uhr schrieb Roland Winklmeier <
roland.m.winklme...@gmail.com>:
> Hey everyone,
>
> First, happy new year!
>
> Second, I switched my nightly build to 5.14 branch and was building debug
> binaries as usual. Configure arguments:
>
> configureArguments=-developer-build -
Hey everyone,
First, happy new year!
Second, I switched my nightly build to 5.14 branch and was building debug
binaries as usual. Configure arguments:
configureArguments=-developer-build -debug -opensource -nomake examples
-nomake tests -confirm-license -opengl desktop -dbus -openssl -I
D:\Downl
13 matches
Mail list logo
