Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>,
	"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH][RFC] base.bbclass: Introduce EXTRA_CONF_PACKAGECONFIG variable
Date: Fri, 25 Mar 2016 11:28:59 +0000	[thread overview]
Message-ID: <1458905339.3073.53.camel@linuxfoundation.org> (raw)
In-Reply-To: <20160325105025.GC2555@jama>

On Fri, 2016-03-25 at 11:50 +0100, Martin Jansa wrote:
> On Wed, Mar 02, 2016 at 12:40:31PM +0000, Burton, Ross wrote:
> > On 27 February 2016 at 22:09, Martin Jansa <martin.jansa@gmail.com>
> > wrote:
> > 
> > > * add separate variable for configuration options generated from
> > >   PACKAGECONFIG setting, this helps other bbclasses and recipes
> > >   to take advantage of PACKAGECONFIG mechanism, without including
> > >   other options from EXTRA_OECONF
> > > * e.g. meta-qt5 recipes are abusing EXTRA_OECONF to get options
> > >   from PACKAGECONFIG:
> > >   EXTRA_QMAKEVARS_PRE +=
> > >   but with
> > >   conf/distro/include/no-static-libs.inc
> > >   it means getting --disable-static as invalid option inside
> > >   EXTRA_QMAKEVARS_PRE as reported by Alexandre Belloni who tried
> > >   to use poky with meta-qt5.
> > > * once we migrate all bbclasses and recipes to
> > > EXTRA_CONF_PACKAGECONFIG
> > >   we should also restrict EXTRA_OECONF append only to
> > > autotools.bbclass
> > >   like I did for cmake.bbclass
> > > 
> > 
> > Sorry, some of us have been a bit busy trying to get M3 stable. 
> >  This does
> > look good and I'm for squeezing it into M3.
> 
> Any update on squeezing this?
> 
> meta-qt5 is still broken with default poky config

I'm a little confused, was there going to be another version with some
tweaked variable names?

Cheers,

Richard


  reply	other threads:[~2016-03-25 11:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27 22:09 [PATCH][RFC] base.bbclass: Introduce EXTRA_CONF_PACKAGECONFIG variable Martin Jansa
2016-03-02 12:38 ` Martin Jansa
2016-03-02 13:11   ` Richard Purdie
2016-03-02 13:24     ` Martin Jansa
2016-03-02 12:40 ` Burton, Ross
2016-03-25 10:50   ` Martin Jansa
2016-03-25 11:28     ` Richard Purdie [this message]
2016-03-25 11:55       ` Martin Jansa
2016-04-18 22:31         ` Otavio Salvador
2016-04-18 22:45           ` Richard Purdie
2016-04-18 22:49             ` Otavio Salvador
2016-04-19  9:50               ` Martin Jansa
2016-04-19 10:31                 ` [PATCH] base.bbclass: Introduce PACKAGECONFIG_CONFARGS variable Martin Jansa
2016-04-19 13:23                   ` Otavio Salvador

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=1458905339.3073.53.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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