Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
	Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] directfb: don't patch pkg-config files
Date: Tue, 30 Jul 2013 15:18:17 +0100	[thread overview]
Message-ID: <10500377.RxauFUiAWr@helios> (raw)
In-Reply-To: <CAP9ODKrysra+zBOTmpYiMMoaoM2gfXqJDRKE1PNa2YNzWpPRxg@mail.gmail.com>

On Friday 19 July 2013 14:52:00 Otavio Salvador wrote:
> On Fri, Jul 19, 2013 at 11:46 AM, Nicolas Dechesne
> 
> <nicolas.dechesne@linaro.org> wrote:
> > On Fri, Jul 19, 2013 at 10:39 AM, André Draszik <andre.draszik@linaro.org>
> > 
> > wrote:
> >> We are currently getting build failures of projects that rely on
> >> being able to access DirectFB's internal include directories, as
> >> returned via pkg-config, since the include paths returned by
> >> pkg-config are incomplete.
> >> 
> >> The reason for that is the patch that is being removed with this
> >> change. It modified the cflags returned by pkg-config in an
> >> incorrect way, causing us to miss important include paths:
> >> 
> >> For reference, pkg-config output with incorrect patch applied:
> >>   ad@bril0118 #513 ~> pkg-config --cflags directfb-internal
> >> 
> >> -D_GNU_SOURCE -D_REENTRANT
> >> -I<builddir>/tmp/sysroots/<machine>/usr/include/directfb
> >> -I<builddir>/tmp/sysroots/<machine>/usr/include
> >> 
> >> Now, with the incorrect patch removed, the output is as expected:
> >>   ad@bril0118 #514 ~> pkg-config --cflags directfb-internal
> >> 
> >> -D_GNU_SOURCE -D_REENTRANT
> >> -I<builddir>/tmp/sysroots/<machine>/usr/include/directfb-internal
> >> -I<builddir>/tmp/sysroots/<machine>/usr/include/directfb
> >> 
> >> Overall, the removed patch is not needed - pkg-config does the right
> >> thing these days and we can simply use the correctly working upstream
> >> versions of all DirectFB .pc files.
> >> 
> >> Signed-off-by: André Draszik <andre.draszik@linaro.org>
> > 
> > i reviewed and tested this patch against a QT4e image build. it looks good
> > to me, and that offending patch being removed seems to come from quite
> > ancient stuff.
> > 
> > Tested-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
> > 
> > any chance this can get into 'dylan', too?
> 
> Paul, I think it is your business ;-)

Indeed. I've added it to my paule/dylan-next branch for testing.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


      reply	other threads:[~2013-07-30 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19  8:39 [PATCH] directfb: don't patch pkg-config files André Draszik
2013-07-19 14:46 ` Nicolas Dechesne
2013-07-19 17:52   ` Otavio Salvador
2013-07-30 14:18     ` Paul Eggleton [this message]

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=10500377.RxauFUiAWr@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=nicolas.dechesne@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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