Re: [Qbs] Set cpp properties for generated cpp files (moc) does not seem to work

2020-05-20 Thread Christian Kandeler
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

Re: [Qbs] Set cpp properties for generated cpp files (moc) does not seem to work

2020-05-20 Thread Christian Gagneraud
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

Re: [Qbs] Set cpp properties for generated cpp files (moc) does not seem to work

2020-05-14 Thread Christian Kandeler
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 >

[Qbs] Set cpp properties for generated cpp files (moc) does not seem to work

2020-05-14 Thread Maximilian Hrabowski
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 { …