All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Crowe <mac@mcrowe.com>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bitbake.conf, module.bbclass: Support opting out of legacy EXTRA_OEMAKE
Date: Fri, 6 Nov 2015 10:30:04 +0000	[thread overview]
Message-ID: <20151106103004.GA7454@mcrowe.com> (raw)
In-Reply-To: <CAJ86T=WxqbJ83S4RESL_oKX9gYNg6-aAPGUYR3btSQBhKQo-1g@mail.gmail.com>

On Friday 06 November 2015 at 01:16:46 -0800, Andre McCurdy wrote:
> On Thu, Nov 5, 2015 at 6:47 AM, Mike Crowe <mac@mcrowe.com> wrote:
> > Give recipes and classes the ability to opt out of EXTRA_OEMAKE
> > containing the legacy value without removing other recipe-specific or
> > local additions.
> 
> Isn't this possible already from within a recipe or class by using
> 
>   EXTRA_OEMAKE = ...
> 
> instead of
> 
>   EXTRA_OEMAKE += ...
> 
> ie what autotools.bbclass, kernel.bbclass and many recipes do already.
> 
> For the specific case of module.bbclass, changing the EXTRA_OEMAKE
> assignment to '=' might require some recipes to be tweaked to so that
> they "inherit module" before adding their own options to EXTRA_OEMAKE,
> but it seems like a cleaner solution?

It would be, but I was afraid of what I might break. I suspect that there
are many unseen third-party and local recipes that inherit module.bbclass.

It would be great to get to the point that EXTRA_OEMAKE is empty by default
but I imagine that the experts are already aware of the difficulties with
doing this which is why the current value has lasted so long.

Mike.


  reply	other threads:[~2015-11-06 10:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05 14:47 [PATCH] bitbake.conf, module.bbclass: Support opting out of legacy EXTRA_OEMAKE Mike Crowe
2015-11-05 16:23 ` Khem Raj
2015-11-05 16:27   ` Christopher Larson
2015-11-05 17:56     ` Khem Raj
2015-11-06  9:16 ` Andre McCurdy
2015-11-06 10:30   ` Mike Crowe [this message]
2015-11-06 13:18     ` Martin Jansa
2015-11-06 14:59       ` Christopher Larson
2015-11-06 16:28         ` Martin Jansa
2015-11-12 12:10     ` Mike Crowe
2015-11-12 20:21       ` Andre McCurdy

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=20151106103004.GA7454@mcrowe.com \
    --to=mac@mcrowe.com \
    --cc=armccurdy@gmail.com \
    --cc=openembedded-core@lists.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.