From: "Peter Kümmel" <syntheticpp@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] ti-gfx: pkg-config should also set parent include dir
Date: Fri, 30 May 2014 23:16:14 +0200 [thread overview]
Message-ID: <5388F51E.10507@gmx.net> (raw)
In-Reply-To: <20140530205741.GE3474@free.fr>
On 30.05.2014 22:57, Yann E. MORIN wrote:
> 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.
>
The cmake code generated by Qt5 is very restrictive
(sysroot/usr/lib/cmake/Qt5Gui/Qt5GuiConfigExtras.cmake):
set(_GL_INCDIRS "/usr/include/GLES2")
find_path(_qt5gui_OPENGL_INCLUDE_DIR GLES2/gl2.h
PATHS ${_GL_INCDIRS} NO_DEFAULT_PATH)
where _GL_INCDIRS is the path list reported by pkg-config.
So specifying an empty Cflags would also fail because
no paths at all are searched.
Peter
next prev parent reply other threads:[~2014-05-30 21:16 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
2014-05-30 21:16 ` Peter Kümmel [this message]
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=5388F51E.10507@gmx.net \
--to=syntheticpp@gmx.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.