On Wed, 20 May 2020 21:44:46 +1200
Christian Gagneraud wrote:
> On Fri, 15 May 2020 at 03:12, Christian Kandeler
> wrote:
> >
> > On Thu, 14 May 2020 14:49:25 +
> > Maximilian Hrabowski wrote:
> >
> > > Isn’t unmocable used to tag cpp/header files that should not be processed
> > > by moc?
On Fri, 15 May 2020 at 03:12, Christian Kandeler
wrote:
>
> On Thu, 14 May 2020 14:49:25 +
> Maximilian Hrabowski wrote:
>
> > Isn’t unmocable used to tag cpp/header files that should not be processed
> > by moc?
>
> Sure, that's why the generated cpp files get it, so they won't get processe
On Thu, 14 May 2020 14:49:25 +
Maximilian Hrabowski wrote:
> Isn’t unmocable used to tag cpp/header files that should not be processed by
> moc?
Sure, that's why the generated cpp files get it, so they won't get processed
again.
Christian
___
Q
On Thu, 14 May 2020 12:22:53 +
Maximilian Hrabowski wrote:
> we have quite a strict warning policy so all warnings are treated as errors
> in our code. This creates problems when including third-party code that
> produces warnings, so usually those files are put in a special group and
> wa
Hi all,
we have quite a strict warning policy so all warnings are treated as errors in
our code. This creates problems when including third-party code that produces
warnings, so usually those files are put in a special group and
warningsAreErrors is turned off:
Group {
…
cpp.treatWarningsAsErr