All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: developer_agl@xtev.cn
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: 转发: About bitbake tasks
Date: Thu, 12 Jul 2018 12:50:47 +0200	[thread overview]
Message-ID: <1993940.Xc2Spn7Ep9@localhost.localdomain> (raw)
In-Reply-To: <009001d419c9$35c39cc0$a14ad640$@xtev.cn>

On Thursday, 12 July 2018 12:15:07 PM CEST developer_agl@xtev.cn wrote:
> I’m new to bitbake. And I have some questions about bitbake tasks mechanism
> and inherit mechanism. If a xxx.bb recipe content like this :
> 
> ##start
> 
> DESCRIPTION = ”xxxxxxxxx”
> 
> XXX_XXXX = “${XXXXXXXX}”
> 
> inherit some_guys
> 
> ##end
> 
> And Bitbake User Manual said that ‘The minimally required class for BitBake
> is the classes/base.bbclass file. The base class is implicitly inherited by
> every recipe.’ So which .bbclass should be parsed first, some_guys.bbclass
> or base.bbclass? I’m really confused about that.

Effectively, base.bbclass will be parsed first, then the lines in the recipe 
up to inherit some_guys, then some_guys.bbclass, and then the lines in the 
recipe that follow (in this case just a comment).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre




  reply	other threads:[~2018-07-12 10:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <008601d419c8$61a20a30$24e61e90$@xtev.cn>
2018-07-12 10:15 ` 转发: About bitbake tasks developer_agl
2018-07-12 10:50   ` Paul Eggleton [this message]
2018-07-13  1:45     ` 答复: " developer_agl

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=1993940.Xc2Spn7Ep9@localhost.localdomain \
    --to=paul.eggleton@linux.intel.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=developer_agl@xtev.cn \
    /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.