Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] ti-gfx: use only -I${includedir} as pkg-config Cflags
Date: Sun, 8 Jun 2014 18:53:03 +0200	[thread overview]
Message-ID: <20140608185303.2e593e07@free-electrons.com> (raw)
In-Reply-To: <1401617908-6489-1-git-send-email-syntheticpp@gmx.net>

Dear Peter K?mmel,

On Sun,  1 Jun 2014 12:18:27 +0200, Peter K?mmel wrote:
> Using only -I${includedir} in common practice.
> 
> Settings only -I${includedir}/GLES2 breaks Qt5's CMake files,
> because at configure time CMake only searchs the paths reported
> by pkg-config, and not even /usr/include is used as default.
> 
> Even though pkg-config strips out standard include path, that's not
> the case with pkgconf (which we are using) in cross-compilation,
> which correctly reports the /usr/include dir prefixed with the
> sysroot.
> 
> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Signed-off-by: Peter K?mmel <syntheticpp@gmx.net>

Both patches applied, thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2014-06-08 16:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01 10:18 [Buildroot] [PATCH 1/2] ti-gfx: use only -I${includedir} as pkg-config Cflags Peter Kümmel
2014-06-01 10:18 ` [Buildroot] [PATCH 2/2] sunxi-mali: " Peter Kümmel
2014-06-03  4:54   ` Peter Kümmel
2014-06-03  4:54 ` [Buildroot] [PATCH 1/2] ti-gfx: " Peter Kümmel
2014-06-08 16:53 ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-06-01  9:50 Peter Kümmel
2014-06-01 10:09 ` Yann E. MORIN
2014-06-01 10:17   ` Peter Kümmel

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=20140608185303.2e593e07@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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