All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Larson <clarson@kergoth.com>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: questions about bitbake world
Date: Tue, 10 Apr 2012 06:58:09 -0700	[thread overview]
Message-ID: <CABcZANm628Wm0TYo45eSjLsVjzpseV=4__he=s=Lz_r1ekyJBw@mail.gmail.com> (raw)
In-Reply-To: <4F83EE3C.8040904@windriver.com>

On Tue, Apr 10, 2012 at 1:24 AM, Robert Yang <liezhi.yang@windriver.com> wrote:
> In the following code:
>
> def buildWorldTargetList(self):
> ...
>        for f in self.status.possible_world:
>            terminal = True
>            pn = self.status.pkg_fn[f]
>
>            for p in pn_provides[pn]:
>                if p.startswith('virtual/'):
>                    parselog.debug(2, "World build skipping %s due to %s
> provider starting with virtual/", f, p)
>                    terminal = False
>                    break
> ...
>
> Does it mean that if a recipe contains:
>
> PROVIDES = "virtual/something"
>
> Then it would not be built until a pkg depends on it? Why we design it in
> this
> way, please?

The original intent with world was that when two recipes provided the
same thing, we'd still only want to build one of them, not both, as
building both can cause problems with stepping on one another in
sysroot, etc.
-- 
Christopher Larson



  reply	other threads:[~2012-04-10 14:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10  8:24 questions about bitbake world Robert Yang
2012-04-10 13:58 ` Chris Larson [this message]
2012-04-10 14:12   ` Robert Yang
2012-04-10 14:15     ` Chris Larson
2012-04-13  0:52       ` Robert Yang
2012-04-13  2:44         ` Christopher Larson

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='CABcZANm628Wm0TYo45eSjLsVjzpseV=4__he=s=Lz_r1ekyJBw@mail.gmail.com' \
    --to=clarson@kergoth.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=liezhi.yang@windriver.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 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.