All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: Dudziak Krzysztof <Krzysztof.Dudziak@gemalto.com>,
	 Yocto-mailing-list <yocto@yoctoproject.org>
Subject: Re: inheriting native.bbclass explicitly
Date: Thu, 13 Sep 2018 12:23:20 +0100	[thread overview]
Message-ID: <CAJTo0LYsU+D+SP3s4Fwg4DYrv++kMmugv1RiVGU4ZFx_aKO=4w@mail.gmail.com> (raw)
In-Reply-To: <VI1PR01MB1070D4F85BC847EF0C3F8651E01A0@VI1PR01MB1070.eurprd01.prod.exchangelabs.com>

CCing the list again.  Please remember to reply to the list.

On 13 September 2018 at 11:42, Dudziak Krzysztof
<Krzysztof.Dudziak@gemalto.com> wrote:
> Is it possible for one Bitbake target to check list and order of classes inherited?

bitbake -e [recipe] will show you what was parsed.

In this situation I wouldn't worry too much.  It's best to use
BBCLASSEXTEND instead of inherit native directly anyway.

Ross


  parent reply	other threads:[~2018-09-13 11:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-13  9:17 inheriting native.bbclass explicitly Dudziak Krzysztof
2018-09-13  9:24 ` Burton, Ross
     [not found]   ` <VI1PR01MB1070A7E32F845C1CBA1D57B6E01A0@VI1PR01MB1070.eurprd01.prod.exchangelabs.com>
2018-09-13  9:38     ` Burton, Ross
     [not found]   ` <VI1PR01MB1070D4F85BC847EF0C3F8651E01A0@VI1PR01MB1070.eurprd01.prod.exchangelabs.com>
2018-09-13 11:23     ` Burton, Ross [this message]
2018-09-13 11:39       ` Dudziak Krzysztof
2018-09-13 12:00         ` Burton, Ross
2018-09-13 12:36           ` Dudziak Krzysztof
2018-09-13 13:05           ` Dudziak Krzysztof
2018-09-13 23:05             ` Andre McCurdy
2018-09-14  8:20               ` Dudziak Krzysztof
2018-09-14 17:23                 ` 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='CAJTo0LYsU+D+SP3s4Fwg4DYrv++kMmugv1RiVGU4ZFx_aKO=4w@mail.gmail.com' \
    --to=ross.burton@intel.com \
    --cc=Krzysztof.Dudziak@gemalto.com \
    --cc=yocto@yoctoproject.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.