[Development] Qt Project 'official way' and maintenance? (Was: Qt 5.1.0 rc2 is out)

Ray Donnelly mingw.android at gmail.com
Wed Jul 3 13:07:40 CEST 2013

> Relevant for Qt

Since Qt is an application framework, I think relevant for Qt implies
"relevant for Qt and any project that uses it".

IMHO the goal should be to fully support build systems to the extent they
work on each platform or dropping that build system.

CI'ing weird corner-case builds is important as they tend to
catch more issues than vanilla builds do (and that most developers also
likely run); ideally you'd have full coverage.

On Wed, Jul 3, 2013 at 11:28 AM, Tor Arne Vestbø
<tor.arne.vestbo at digia.com>wrote:

> On 7/3/13 12:12 , Laszlo Papp wrote:
> > On Mon, Jul 1, 2013 at 2:10 PM, Tor Arne Vestbø
> > <tor.arne.vestbo at digia.com <mailto:tor.arne.vestbo at digia.com>> wrote:
> >
> >     There is also the question of platform support. Is cmake as relevant
> on
> >     Windows or OSX as it is on Linux? More so?
> >
> >
> > Not sure what exactly you mean by relevant, but cmake is a
> > /cross/-/platform/, open-source build system. It has been used on
> > Windows and OS X extensively out there for a while.
> Relevant for Qt.
> What percentage of Qt developers develop on Windows?
> Out of those, what percentage use cmake over qmake?
> At some point the cost of maintaining (blocking CI integration e.g.) a
> build system (or any feature) that has a low relevance on a given
> platform becomes higher than the benefit.
> tor arne
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130703/4d56c1a9/attachment.html>

More information about the Development mailing list