From: Marcin Juszkiewicz <openembedded@hrw.one.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Bitbake: say who you are cooking
Date: Wed, 18 Oct 2006 12:40:30 +0200 [thread overview]
Message-ID: <200610181240.31042.openembedded@hrw.one.pl> (raw)
In-Reply-To: <b9481e140610180154r5a3c5c0do543863a9b0b4c059@mail.gmail.com>
Dnia środa, 18 października 2006 10:54, Nicolas FR napisał:
> When we start to bitbake a recipe, let's say "bitbake foo", bitbakes
> starts compiling dependencies without telling which version of foo he
> will finally compile.
>
> I find this frustating, because quite often (wrong preferred provider,
> ...) I end up bitbaking the wrong version of a recipe, and bb won't
> tell you this before having successfully compiled all the
> dependencies.
>
> It would be nice to have bitbake print which version he will bitbake
> before actually compiling the dependencies.
"bitbake --dry-run foo" do what you seek for.
--
JID: hrw-jabber.org
OpenEmbedded developer/consultant
next prev parent reply other threads:[~2006-10-18 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 8:54 Bitbake: say who you are cooking Nicolas FR
2006-10-18 10:40 ` Marcin Juszkiewicz [this message]
2006-10-18 18:19 ` Nicolas FR
2006-10-18 18:41 ` Nicolas FR
2006-10-18 19:16 ` Paul Sokolovsky
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=200610181240.31042.openembedded@hrw.one.pl \
--to=openembedded@hrw.one.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox