From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: build dependency cycles in openembedded
Date: Sun, 24 Feb 2013 00:12:59 -0800 [thread overview]
Message-ID: <20130224081258.GD3154@sakrah.homelinux.org> (raw)
In-Reply-To: <20130219104653.30650.95226@hoothoot>
On (19/02/13 11:46), Johannes Schauer wrote:
> Hi,
>
> Quoting Andreas Müller (2013-02-18 21:15:43)
> > FWIW long time ago in meta-oe commit 5b8522e3b592c96ec9325aff4bbaa68972e52d5b
> > gvfs-gdu-volume-monitor was spitted out into an own recipe to break
> > dependency loop for gvfs.
>
> If I read this correctly, then this means that for some software packages,
> multiple bitbake recipes exist for the purpose of breaking dependency cycles?
>
> How does the generation of build order work? Which algorithm handles the
> selection of recipes such that build dependency cycles are avoided? And once a
> recipe which was used to break a dependency cycle was compiled, how is the
> recompilation of the *full* package scheduled?
bitbake handles the built dependencies and runqueue generation which
decided the order or task execution. You should read about bitbkake
internals if you are interested in internal functioning of dep
resolution in bitbake.
prev parent reply other threads:[~2013-02-24 8:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 9:41 build dependency cycles in openembedded Johannes Schauer
2013-02-18 12:26 ` Takeshi Hamasaki
2013-02-18 14:20 ` Johannes Schauer
2013-02-18 15:07 ` Takeshi Hamasaki
2013-02-18 16:53 ` Johannes Schauer
2013-02-18 17:22 ` Marko Lindqvist
2013-02-18 18:54 ` Johannes Schauer
2013-02-18 20:15 ` Andreas Müller
2013-02-19 10:46 ` Johannes Schauer
2013-02-24 8:12 ` Khem Raj [this message]
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=20130224081258.GD3154@sakrah.homelinux.org \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@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.