Hello, you can find the generated modules in the build directory.
$ pwd
/Users/abbapoh/Programming/qt5/alien/qbs/examples/helloworld-qt
$ qbs
Build graph does not yet exist for configuration 'default'. Starting from
scratch.
Resolving project for configuration default
Setting up Qt at
On Wed, 20 May 2020 at 22:39, Christian Gagneraud wrote:
> I understand the cons arguments, and i agree with that, this should be
> under user's control.
>
> A variation could be:
>
> property bool useSystemInclude = name === "Qt.core" ? false :
> Qt.core.useSystemInclude
> Properties {
>
On Wed, 20 May 2020 at 22:24, Christian Kandeler
wrote:
>
> On Wed, 20 May 2020 22:11:20 +1200
> Christian Gagneraud wrote:
>
> > Couldn't find any definite answer about using '-isystem' to avoid the
> > compiler to report warning as error in 3rd party headers (qt, gtest,
> > ...).
> > Looking
On Wed, 20 May 2020 22:11:20 +1200
Christian Gagneraud wrote:
> Couldn't find any definite answer about using '-isystem' to avoid the
> compiler to report warning as error in 3rd party headers (qt, gtest,
> ...).
> Looking at the cpp module, i can see some logic, but I can't seem to
> find a way
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
Hi there,
Couldn't find any definite answer about using '-isystem' to avoid the
compiler to report warning as error in 3rd party headers (qt, gtest,
...).
Looking at the cpp module, i can see some logic, but I can't seem to
find a way to force the use of isystem.
The only suggestion I found was
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
