On 10/14/22 03:15, Eike Ziller wrote:
However, there are ways to enforce the use of unique header guards. clang-tidy
has an extensible header guard check that can be customized per-project, and
plugin loading functionality. Qt could create a clang-tidy plugin that sets up
this header guard che
On 10/13/22 10:42, Jean-Michaël Celerier wrote:
>The only way you’d have a strong case with this is if it has some
other significant benefit, like compilation speedup.
The main benefit to me is that it entirely removes possibilities for
conflict due to headers having the same name. At least Qt
On 10/10/22 05:55, Volker Hilsheimer via Development wrote:
Hi,
We are using `#pragma once` in a number of examples and tests in the Qt source
tree, but I don’t think we have officially endorsed it in favour of explicit
include guards.
#pragma once is “non-standard but widely supported” [1],
On 8/10/21 3:13 AM, Joerg Bornemann wrote:
Hi there!
I'd like to nominate Craig Scott as approver.
+1 from me. As a fellow CMake maintainer, I can vouch for his excellent
work and attention to detail.
Kyle
___
Development mailing list
Development
On 5/19/21 11:57 AM, Lisandro Damián Nicanor Pérez Meyer wrote:
Discord is not free software, so it does not align well with a free
software project.
+1
Kyle
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listin
On 5/5/21 1:58 PM, Thiago Macieira wrote:
3.16.0 was tagged on Nov 2019, which is a little too close for comfort. For
comparison, we require GCC 8, which was released in May 2018.
However, given that no one has apparently complained and that upgrading cmake
is far easier than the compiler, I hav
Great news!
Are you using Ninja Multi-Config yet? :)
Kyle
On Tue, Feb 11, 2020 at 10:40 AM Alexandru Croitor
wrote:
>
> I published the Qt 6 CMake Port slides that I presented at Qt Contributor
> Summit in 2019.
>
> https://github.com/alcroito/qt6_cmake_port_slides
>
> It might be a bit outdat
On Wed, 2020-01-29 at 14:07 +, Khuram Ali via Development wrote:
> Hi,
>
> I haven't requested to reset my Qt Account password. It seems some
> malicious attempt. Please advise. thank you!
I got it too. Everyone on the mailing list just received it.
Kyle
On Wed, 2020-01-29 at 13:44 +, Cristián Maureira-Fredes wrote:
> Hey Kyle,
>
> thanks for your answer,
> out of curiosity, are there some past business models
> that failed inside Kitware? or it has been support only since
> the beginning?
>
> What I'm trying to find out is that if maybe some
On Wed, 2020-01-29 at 08:20 +0100, Elvis Stansvik wrote:
> Just want to add here: Even if CMake is probably the Kitware project
> with the largest number of users if counting developers, I don't
> think
> it's their flagship product. That would be the VTK framework (2500
> classes, 1 MLoC) and asso
On Fri, 2019-11-08 at 20:35 +, Alessandro Portale wrote:
> There is more. Much of his time with us, he spent on adding features
> upstream to CMake which we thought were missing in Qt's future build
> tool: PCH support, Unity/Jumbo builds, etc.. CMake users outside Qt's
> ecosystem are certainl
On Fri, 2019-10-18 at 17:09 +0100, Sérgio Martins wrote:
> Make git move the star for you at checkout time (similarly to its
> CRLF options).
> Git "just" needs C++ code model support.
I like this idea. While we're at it, let's also add automatic i18n
support to Git, so that developers can read an
On Thu, 2019-10-17 at 20:01 +, Martin Smith wrote:
> But that argues for not allowing the comma.
>
> QObject* x;
> QObject* y;
>
> I've always done it that way.
+1 for not allowing the comma. It's not as much of an issue for simple
types (int x, y), but combining it with pointers and referen
On Thu, 2019-09-19 at 21:50 +0200, André Pönitz wrote:
> Having constexpr or not on certain functions could depend on the
> actual
> compiler in some cases, providing the performance benefits for the
> compilers supporting it, and still keeping platforms with unsuitable
> compilers alive.
As a ge
On Wed, 2019-08-21 at 17:25 -0400, Kyle Edwards wrote:
> If you don't own the copyright, and you can't get permission from the
> copyright holder, then my guess would be no, unless you can
> successfully argue that the MSVC runtime *is* a system library (even
> though it&
On Wed, 2019-08-21 at 22:43 +0200, Kai Pastor, DG0YT wrote:
> Is it possible to distribute a GPL-3 licensed application this way?
> After all, these DLLs are neither system libraries nor are they are
> offered under compatible terms.
IANAL. If you own the copyright then you can of course license
On Wed, 2019-08-21 at 21:22 +0200, Elvis Stansvik wrote:
> Why not just ship those DLLs? I wouldn't call that "verboten"
> (forbidden), just a bit more to do for deployment.
It's not "verboten", but it's also not as straightforward as
redistributing free software like MinGW.
From https://docs.mic
On Mon, 2019-06-17 at 11:45 -0400, Matthew Woehlke wrote:
> Building both shared and static in a single tree with CMake is
> perfectly
> do-able. See e.g. LCM, which does so. (The main caveat is that they
> need
> different target names.)
And both targets have to have their OUTPUT_NAME property se
On Tue, 2019-06-11 at 18:30 +0200, Giuseppe D'Angelo via Development
wrote:
> > Is this intended? Or would it make sense to move the documentation
> > to
> > QMetaObject?
> Well, also Q_OBJECT itself, Q_SIGNALS/Q_SLOTS, etc. appear in
> qobjectdefs.h, yet obviously the right place for documented t
Hello all,
I am currently working on improving Qt's CMake support, and I've written
some rather complicated logic that I want to test thoroughly -
specifically, I want to make sure that an exact list of plugins that I've
requested has been statically loaded, no more, and no less. The easiest way
t
On Fri, 2018-10-12 at 20:32 +0200, Jean-Michaël Celerier wrote:
> it would be so nice to add them ! currently I have to use the
> following chthonic horror: https://github.com/OSSIA/score/blob/maste
> r/base/app/StaticApp.cmake
Yep, this is exactly what I'm trying to fix!
Kyle_
Hello everyone,
New Qt developer here. I'm trying to improve Qt's support for static
builds using CMake - specifically, encoding transitive dependencies in
the *Config.cmake files. I see that these files already have inter-
module dependencies encoded in the exported targets'
INTERFACE_LINK_LIBRAR
22 matches
Mail list logo
