[Development] New Module Request: QtGeniviExtras

Turunen Tuukka tuukka.turunen at theqtcompany.com
Thu Aug 13 12:29:31 CEST 2015

> -----Original Message-----
> From: development-bounces+tuukka.turunen=theqtcompany.com at qt-
> project.org [mailto:development-
> bounces+tuukka.turunen=theqtcompany.com at qt-project.org] On Behalf Of
> Dominik Holland
> Sent: 13. elokuuta 2015 12:37
> To: André Somers <andre at familiesomers.nl>
> Cc: development at qt-project.org
> Subject: Re: [Development] New Module Request: QtGeniviExtras
> On 08/13/2015 11:08 AM, André Somers wrote:
> >
> >
> >> IMHO the users of QtGeniviExtras and the DLT logging are totally
> >> aware of how the system works and want to have full control over it.
> >> DLT is only known in the automotive space and there it's only used
> >> for GENIVI linux based systems. So i think we talk about a logging
> >> solution which 90% of the qt community don't know or won't ever use.
> >> I really don't think this is something which should be integrated
> >> into qtcore, and should be totally fine to live in it's own
> >> repository and in the end it's very similar of what the other extra
> >> repositories currently do, components which doesn't fit and are
> >> platform specific are in extras
> >>
> >
> > Just wondering... If so you expect so few users to use this, what is the
> benefit of having this as a Qt module? Would it not be better to keep things
> that only users from specialized niche markets use in specialized libs aimed
> at those users?
> >
> > André
> >
> But's what i'm targeting, the module is meant for these users and it will
> contain multiple specialized libs.
> The benefit of having it as a module is that it can use the same build
> infrastructure, it's shipped with Qt, integrated in qmake/cmake, using the
> same Documentation. It should be part of Qt, but it's only needed on specific
> platforms, like all the other extra repositories. I think nobody cares about the
> qtwinextras beside the people developing for it.
> The module shouldn't be contained in any Desktop Installer or on mobile
> platforms, it's just available on automotive platforms and their SDKs

I think it is fine to create the requested repo for new module. Depending on the need it can then either be included or not be included in the release packages. It is better to keep these enablers within the Qt systems than in a separate location somewhere.

Like Thiago and other have pointed out we of course would like to have the content of the new module well suited for Qt before it can become part of a Qt release. I think the best way to achieve this is to do the work within the Qt Project and Qt repositories, after which we can then at some point have a module that is well fit for Qt and its purpose.



More information about the Development mailing list