public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Denys Dmytriyenko" <denis@denix.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] can i blacklist a particular .bbclass file when there are more than one?
Date: Thu, 30 Apr 2020 13:01:16 -0400	[thread overview]
Message-ID: <20200430170116.GT11927@denix.org> (raw)
In-Reply-To: <alpine.LFD.2.21.2004300945580.19276@localhost.localdomain>

On Thu, Apr 30, 2020 at 09:49:32AM -0400, Robert P. J. Day wrote:
> 
>   given an odd collection of layers wherein there are multiple
> instances of a particular .bbclass file, it turns out that all of the
> recipes i'm interested in build with an older version of the class
> file, and all but one build consulting the newer form of the file
> contained in another layer, so is there any way to blacklist a
> particular class file, either globally or even on a per-recipe basis?
> 
>   i realize this is really, really bad design style, but it will give
> me the chance to use the proper class file for most of the recipes
> while i debug the problematic recipe.

The order of BBLAYERS in bblayers.conf affects which class will be used 
globally for the build. Don't believe can be done per-recipe.

BTW, would these generic questions better belong to yocto list istead of 
openembedded-core?

-- 
Denys

  reply	other threads:[~2020-04-30 17:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 13:49 can i blacklist a particular .bbclass file when there are more than one? Robert P. J. Day
2020-04-30 17:01 ` Denys Dmytriyenko [this message]
2020-05-04  8:38   ` [OE-core] " Quentin Schulz

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=20200430170116.GT11927@denix.org \
    --to=denis@denix.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox