09.09.2019, 17:15, "Richard Weickelt" :
> Hello,
>
> I would like to build and test Qbs against development snapshots of Qt in
> order to prevent disasters like https://bugreports.qt.io/browse/QBS-1492 from
> happening again.
>
> Are there any snapshots of the Qt SDK available in some form? Som
On Monday, 9 September 2019 14:07:59 PDT Lisandro Damián Nicanor Pérez Meyer
wrote:
> Is this acceptable? I really think it is not, but...
It's not. Requiring people to build LLVM + Clang, whcih is huge, is not
something we should do.
Please work around.
--
Thiago Macieira - thiago.macieira (
Hi! It seems that now Qt Creator requires a patched Clang build in
order to build the ClangFormat plugin:
https://bugreports.qt.io/browse/QTCREATORBUG-22404
https://bugreports.qt.io/browse/QTCREATORBUG-22923
The patch in itself hasn't been even accepted in clang's master branch:
https://reviews.
Hi Florian,
We'll run the Contributor Summit in Berlin Adlershof. I started to create a
wiki page for this, expect more updates in the next days!
https://wiki.qt.io/Qt_Contributors_Summit_2019
Regards
Kai
> -Original Message-
> From: Development On Behalf Of
> Florian Bruhin
> Sent:
Hey Tuukka,
On Thu, Sep 05, 2019 at 11:23:28AM +, Tuukka Turunen wrote:
> We are working on getting the registration open in the coming weeks as well
> as more details of the planned structure.
I don't mean to be pushy, but is there any chance you could share a more exact
location already, if
On Monday, 9 September 2019 05:44:15 PDT Mutz, Marc via Development wrote:
> 1. For the writer of the code, having to add the version check means
> researching the history of a feature to unearth the value with which the
> feature was originally added. cppreference.com is not very helpful in
> that
Hello,
I would like to build and test Qbs against development snapshots of Qt in order
to prevent disasters like https://bugreports.qt.io/browse/QBS-1492 from
happening again.
Are there any snapshots of the Qt SDK available in some form? Something like
the 7z packages used by the installer too
Hi,
Qt uses C++ feature test macros (__cpp_...) to detect post-C++11
features, and the status quo is that we only support compilers that
provide them.
This proposal does not intend to change this.
This proposal intends to change the de-facto status quo in how we check
these feature macros.
Hi,
just for the record, I would like to point out that the implications on
tooling need to be considered:
The clang-C-API (libclang) as used by Qt for Python, qdoc (and
potentially lupdate) does not know about inline namespaces AFAIK; the
code would have to ported to the Clang C++ API.
Regar
