Hi all,
As some of you may already know, The Qt Company has posted a blog post
about "Qt offers" and Lars has send an email about it to the development
mailing list.
It seems that the interest mailing list has been forgotten.
Since the subject of the blog post and Lars' email is of interest to
I agree with Ulf, sometimes stepping into release sources gives you a rough
idea of what is going on, assess whether you can fix it and if it is
reasonable to go through the whole process of building/debugging your own
Qt version. That's not what I usually do in my work, so it takes an effort.
Hi,
is there a way to add a qt.conf into the qrc resources to only overwrite a
single part (Translations and Qml2Imports) without affecting the whole
discovering of plugins, lib, etc inside Qt Creator? why is non declared part
inside a qt.conf modify the current value? Does it set the default
> Stepping into -O2 builds (-O3 for QtCore and QtGui) is painful at best. The
> debug information we provide is not usable for more than getting backtraces to
> help the developer solving issues.
Stepping into optimized builds is kind of an annoyance but, at least for
me, it is much less of a
On Monday, 27 January 2020 07:12:16 PST Kai Köhne wrote:
> Well, actually we do provide debug information for our binary builds on
> Linux; just select the "Debug Information Files" in the online installer.
Stepping into -O2 builds (-O3 for QtCore and QtGui) is painful at best. The
debug
> -Ursprüngliche Nachricht-
> Von: Interest Im Auftrag von Thiago
> Macieira
> [...]
> You're not missing anything. The MinGW binaries now match the Linux ones:
> no debug libraries anymore.
Well, actually we do provide debug information for our binary builds on Linux;
just select the
