All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: Missing includes in STAGING_INCDIR
Date: Tue, 04 Mar 2008 16:40:05 +0000	[thread overview]
Message-ID: <1204648806.8117.6.camel@dax.rpnet.com> (raw)
In-Reply-To: <200803041729.55760.thomas.cooksey@trolltech.com>

On Tue, 2008-03-04 at 17:29 +0100, Tom Cooksey wrote:
> On Tuesday 04 March 2008 17:05:09 Richard Purdie wrote:
> > On Tue, 2008-03-04 at 13:56 +0100, Tom Cooksey wrote:
> > > Yup, we like pkgconfig too, saves us a lot of work. :-) Sadly, we have to support 
> > > qt being built on 3rd party toolchains we have no access to and therefore no
> > > way to modify. pkg-config caused a headache for support so we've dropped it
> > > by default when cross-compiling. Hopefully we'll re-enable it in the future as
> > > the pkg-config devs seem to be working on the problem, providing an env 
> > > variable you can use to set a sysroot prefix (PKG_CONFIG_SYSROOT).
> > 
> > Just for reference, it was OE users (well, Poky) who argued for that to
> > be introduced into pkgconfig to escape the mangling that we used to
> > do[1] ;-)
> > 
> > [1] We're literally in the process of removing that today.
> 
> Awesome! Well argued. :-) Does that mean PKG_CONFIG_SYSROOT is stable
> enough now to be used in anger?

Poky has been using it for a while without too many problems and OE has
just switched to it. It seems to work well although it does highlight
there are some badly written pkgconfig files around...

Cheers,

Richard





      reply	other threads:[~2008-03-04 16:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04 11:40 Missing includes in STAGING_INCDIR Tom Cooksey
2008-03-04 11:47 ` Michael 'Mickey' Lauer
2008-03-04 12:20   ` Tom Cooksey
2008-03-04 12:25     ` Michael 'Mickey' Lauer
2008-03-04 12:56       ` Tom Cooksey
2008-03-04 16:05         ` Richard Purdie
2008-03-04 16:29           ` Tom Cooksey
2008-03-04 16:40             ` Richard Purdie [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=1204648806.8117.6.camel@dax.rpnet.com \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    /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.