Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] ti-gfx: pkg-config should also set parent include dir
Date: Fri, 30 May 2014 22:57:41 +0200	[thread overview]
Message-ID: <20140530205741.GE3474@free.fr> (raw)
In-Reply-To: <5388ECDC.6050909@gmx.net>

Peter, All,

On 2014-05-30 22:41 +0200, Peter K?mmel spake thusly:
> In short: anybody assumes "#include <GLES2/gl2.h>" works when the search
> paths of pkg-config are used. But when pkg-config reports /usr/include/GLES2
> gl2.h could not be found, because there is no /usr/include/GLES2/GLES2/gl2.h.
> 
> Until now this doesn't pop up because by chance the directory GLES2
> resides in /usr/include and this path is added by most by build systems.
> But the cmake configure scripts of Qt5 test for "GLES2/gl2.h" only in the path
> reported by pkg-config.

And what if we do not specify any Cflags in the .pc? Is Qt5's configure
script happy with that?

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2014-05-30 20:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-30 15:00 [Buildroot] [PATCH 1/1] ti-gfx: pkg-config should also set parent include dir Peter Kümmel
2014-05-30 15:31 ` Spenser Gilliland
2014-05-30 15:55   ` Peter Kümmel
2014-05-30 19:57     ` Spenser Gilliland
2014-05-30 20:27       ` Thomas Petazzoni
2014-05-30 20:41         ` Peter Kümmel
2014-05-30 20:52           ` Peter Korsgaard
2014-05-30 21:29             ` Peter Kümmel
2014-05-30 21:41               ` Peter Korsgaard
2014-05-31  4:34                 ` Peter Kümmel
2014-05-31  9:37                   ` Yann E. MORIN
2014-05-31  9:39                     ` Yann E. MORIN
2014-05-31 11:48                       ` Peter Korsgaard
2014-05-30 20:57           ` Yann E. MORIN [this message]
2014-05-30 21:16             ` Peter Kümmel
2014-05-30 21:23               ` Yann E. MORIN
2014-05-30 21:39                 ` Peter Kümmel
2014-05-30 21:42                   ` Yann E. MORIN
2014-05-30 20:32       ` 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=20140530205741.GE3474@free.fr \
    --to=yann.morin.1998@free.fr \
    --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