All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Schauer <j.schauer@email.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: build dependency cycles in openembedded
Date: Mon, 18 Feb 2013 15:20:26 +0100	[thread overview]
Message-ID: <20130218142026.7849.12017@hoothoot> (raw)
In-Reply-To: <CAPESJy7YAk9vj56pPkATdJO95xv8gwysyRyA9vyEq5YX-MyD=Q@mail.gmail.com>

Hi,

Quoting Takeshi Hamasaki (2013-02-18 13:26:38)
> you can find the line like:
> DEPENDS = "XXXXXX-native"
> in some recipes.
> 
> So, you can describe dependency to native tools from target build if necessary.

Sure, when cross compiling you can satisfy lots of dependencies by native
binaries but others need the foreign version. In Debian based distribution,
this distinction for cross build dependency resolution is made using
Multi-Arch.

Since some of the cross build dependencies can be satisfied by (already
available) native tools, the dependency cycle situation is *much* less severe
during cross compilation than it is during native compilation.

But still, even when one wants to cross compile a native, minimal Debian build
system (just containing the init, shell and compiler) one runs into build
dependency cycles because some dependencies have to be satisfied by foreign
(not yet built) binaries and thereby creating some dependency cycles.

Is it different in OpenEmbedded?

cheers, josch



  reply	other threads:[~2013-02-18 14:36 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 [this message]
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

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=20130218142026.7849.12017@hoothoot \
    --to=j.schauer@email.de \
    --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.