On 1/27/25 18:07, Alex Shaw wrote:
Is anyone interested in seeing this officially added to Qt?
That seems interesting. Do I understand correctly that the devcontainer
spec [1] would go into a repo different from vsccodeext?
And vscodeext would merely announce its existence?
Cheers,
Joerg
On 11/14/24 09:14, Sune Vuorela wrote:
Or is it more specific that you think that the backports-provided cmake will
not be stable enough for building software?
CMake is generally very good in regards to compatibility and building older and
newer projects.
The change in Debian unstable from
On 9/25/24 08:53, Marcus Tillmanns via Development wrote:
I’d like to nominate Orkun Tokdemir for approver status. He has been working on
the Visual Studio Code extensions from the beginning and is currently the main
Developer of it. He has also worked on the CMake side of Qt for a while.
You
Hi,
we'd like to change the format of qt_attribution.json files a tiny bit.
Currently, the Copyright key takes a string as value, and for
readability purposes we used invalid JSON like this:
"Copyright": "Copyright (C) 2002, 2003 CodeFactory AB
Copyright (C) 2004, 2005 Red Hat, Inc."
We w
On 8/1/23 14:22, Haowei Hsu wrote:
However, it turns out that there is an error in the Step 7:
You're doing a prefix build [1] but you did not build & install before
building the docs. The error indicates a missing file in the install prefix.
Try a non-prefix build instead. Without configur
On 2/15/23 14:46, Jörg Bornemann via Development wrote:
we're proposing a new QUIP: License specification in Qt's modules
Please review https://codereview.qt-project.org/c/meta/quips/+/436096
And because QUIP 3 suggests that the initial text is also sent to the
mailing list - here's the docu
On 11/21/22 03:38, Thiago Macieira wrote:
I've just finished a qtbase build on Linux with two sub-architectures and the
symbol comparison of all the resulting libraries has shown zero difference.
Tomorrow I will test all other modules (except qtwebengine). The code is ugly,
so I'd appreciate gui