Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qt5: Disable pkg-config usage for cross-building
Date: Fri, 23 Sep 2016 07:28:11 +0000	[thread overview]
Message-ID: <1474615682.2562.11.camel@synopsys.com> (raw)
In-Reply-To: <20160923081921.189fd5e4@free-electrons.com>

Hi Thomas,

On Fri, 2016-09-23 at 08:19 +0200, Thomas Petazzoni wrote:
> Hello,
> 
> On Fri, 23 Sep 2016 06:12:44 +0000, Alexey Brodkin wrote:
> 
> > 
> > > 
> > > Alexey, have you tried the other approaches I outlined in the thread
> > > where the initial discussion took place???
> > 
> > Well I don't like removal of pkg-config usage either but...
> > Another approach with setting?QMAKE_CFLAGS_ISYSTEM to "" may work as well
> > (even thought I haven't tried it yet) but that will mean people using
> > buildroot-built toolchain for building their Qt5 apps will see those
> > compiler warnings about "wrong" stuff in system headers. In the end that's why
> > this "-isystem" was introduced in the first place.
> 
> Which warning will they see? I don't quite get why they would see a
> warning,

I don't have an example handy but maybe this sheds some light on that
https://gcc.gnu.org/onlinedocs/cpp/System-Headers.h
tml?

> and still fail to understand why qmake uses -isystem.

Again I would assume that's to mute warnings that have nothing to
do with Qt itself or user's code.

-Alexey

  reply	other threads:[~2016-09-23  7:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22 19:48 [Buildroot] [PATCH] qt5: Disable pkg-config usage for cross-building Alexey Brodkin
2016-09-22 20:58 ` Yann E. MORIN
2016-09-23  5:57   ` Thomas Petazzoni
2016-09-23  6:12     ` Alexey Brodkin
2016-09-23  6:19       ` Thomas Petazzoni
2016-09-23  7:28         ` Alexey Brodkin [this message]
2016-09-23  9:38           ` Alexey Brodkin
2016-09-24  6:05             ` Fabián Inostroza

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1474615682.2562.11.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox