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: Sat, 31 May 2014 06:34:18 +0200 [thread overview]
Message-ID: <53895BCA.8020900@gmx.net> (raw)
In-Reply-To: <87ha476j19.fsf@dell.be.48ers.dk>
On 30.05.2014 23:41, Peter Korsgaard wrote:
>>>>>> "Peter" == Peter K?mmel <syntheticpp@gmx.net> writes:
>
> Hi,
>
> > I don't know if Ubuntu is a reference here, but when you install gles2
> > sudo apt-get install libgles2-mesa-dev
> > and have a look at the.pc file,
> > cat /usr/lib/x86_64-linux-gnu/pkgconfig/glesv2.pc
> > (or gl.pc) you see, that there also the path to the dir containing GLES2 is set:
>
> > prefix=/usr
> > exec_prefix=${prefix}
> > libdir=${prefix}/lib/x86_64-linux-gnu
> > includedir=${prefix}/include
>
> > Name: glesv2
> > Description: Mesa OpenGL ES 2.0 library
> > Requires.private:
> > Version: 9.0.3
> > Libs: -L${libdir} -lGLESv2
> > Libs.private: -lm -lpthread -ldl
> > Cflags: -I${includedir}
>
> And what does pkg-config --cflags glesv2.pc show? pkg-config afaik
> strips -I<standard-include-dir> away.
>
Yes, on the desktop pkg-config --cflags glesv2.pc shows nothing.
But the generated cmake code for desktop Qt5 does not have the
find_package() command which fails when cross-compiling.
(And I don't wanna figure out why the cmake file is different
for the desktop).
The pkg-config used by buildroot lists the path in sysroot.
Anyway, seems Cflags: -I${includedir} is the minimum for all
GL config files.
Peter
next prev parent reply other threads:[~2014-05-31 4:34 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 [this message]
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
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=53895BCA.8020900@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox