Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: how much can bitbake tell me about my upcoming build?
Date: Wed, 28 Mar 2012 00:19:27 +0100	[thread overview]
Message-ID: <1332890367.28414.187.camel@ted> (raw)
In-Reply-To: <alpine.DEB.2.02.1203271734090.7770@oneiric>

On Tue, 2012-03-27 at 17:48 -0400, Robert P. J. Day wrote:
> so, let's say i've decided to use oe-core to build a qemux86 image:
> 
> $ . oe-core/oe-init-build-env builds/qemux86
> 
> before i go *any* further (before i even decide which image i'm going
> to bake), how much can bitbake tell me about this configuration?
> 
>   i know
> 
> $ bitbake -e
> 
> can tell me my current environment, that's certainly useful.
> 
>   i can also use
> 
> $ bitbake -s
> 
> to show me the current and preferred versions of all packages (related
> strictly to the current MACHINE setting in local.conf, correct?)
> 
>   what other info can i get out of bitbake?  what about image-specific
> info?  is there a way to list the packages required for a given image?
> some equivalent of
> 
> $ bitbake -s core-image-sato
> 
>   what about a command that lists the available images without having
> to peruse the oe-core "images" directories?  and what about any of the
> other bitbake-related utilities?  i can see "bitbake-layers" being
> pretty useful.
> 
>   in short, without starting an actual build, how much information can
> i extract using bitbake and bitbake-related utilities?

Well, there are:

bitbake -g (and look at task-depends.dot)
bitbake -g -u depexp
bitbake core-image-sato -n (dry run)

which will give some interesting info.

> p.s.  one thing i'd like is to be able to ask how much source i would
> need to download for a given build before i start.  is there any way
> to do that?

Not that I'm aware of since the SRC_URIs don't say how big a download
is, nor are they ever likely to.

Cheers,

Richard




  reply	other threads:[~2012-03-27 23:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 21:48 how much can bitbake tell me about my upcoming build? Robert P. J. Day
2012-03-27 23:19 ` Richard Purdie [this message]
2012-03-27 23:41   ` Robert P. J. Day

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=1332890367.28414.187.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@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