Bitbake: say who you are cooking

Bitbake: say who you are cooking

[Nicolas FR]

Hi,

A suggestion for Bitbake:

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.

Eg:
# bitbake foo
Note: parsing foo_2.0.1.bb
...

What do you think?

Re: Bitbake: say who you are cooking

[Marcin Juszkiewicz]

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

Re: Bitbake: say who you are cooking

[Nicolas FR]

This is more verbose, but still it will tell me what version of the
package it will build only after having built all the dependencies. It
should tell the version it will compile before going with the
dependencies.

For example, just after the line:
NOTE: build 200610182011: started

Here is the output of a "bitbake --dry-run wpa-gui":

root@zhost:/opt/OE/build# bitbake --dry-run wpa-gui
NOTE: Using cache in '/opt/OE/build/tmp/cache'
NOTE: Handling BitBake files: \ (4004/4004) [100 %]
NOTE: Parsing finished. 0 cached, 3880 parsed, 124 skipped, 0 masked.

NOTE: build 200610182011: started

OE Build Configuration:
BB_VERSION     = "1.6.0"
OE_REVISION    = "cf30bb94f4666250edc553470fefa4459ef0af1e"
TARGET_ARCH    = "arm"
TARGET_OS      = "linux-gnueabi"
MACHINE        = "spitz"
DISTRO         = "angstrom"
DISTRO_VERSION = "test-20061018"
TARGET_FPU     = "soft"

NOTE: package binutils-cross-2.17: started
NOTE: package binutils-cross-2.17: completed
NOTE: preferred version 2.5 of glibc not available
NOTE: package uicmoc3-native-3.3.5: started
NOTE: package uicmoc3-native-3.3.5: completed
NOTE: package mysql-native-4.1.18: started
NOTE: package mysql-native-4.1.18: completed
NOTE: package mysql-4.1.18: started
NOTE: package mysql-4.1.18: completed
NOTE: package qt-x11-free-3.3.6: started
NOTE: package qt-x11-free-3.3.6: completed
NOTE: package wpa-gui-0.4.8: started
NOTE: package wpa-gui-0.4.8: completed
NOTE: build 200610182011: completed
Build statistics:
  Attempted builds: 6


> "bitbake --dry-run foo" do what you seek for.

Re: Bitbake: say who you are cooking

[Nicolas FR]

Oops, I may have written too fast. I thought it had really compiled the recipe!

;)

Ok so basically that WAS what I was looking for!


On 10/18/06, Nicolas FR <nicolasfr@gmail.com> wrote:
> This is more verbose, but still it will tell me what version of the
> package it will build only after having built all the dependencies. It
> should tell the version it will compile before going with the
> dependencies.

Re: Bitbake: say who you are cooking

[Paul Sokolovsky]

Hello Nicolas,

Wednesday, October 18, 2006, 9:19:37 PM, you wrote:

> This is more verbose, but still it will tell me what version of the
> package it will build only after having built all the dependencies. It
> should tell the version it will compile before going with the
> dependencies.

  Well, there're pretty many things which bitbake really should do,
including many small good things like this ;-).

  From a quick look, it would be relatively easy to do this, at least
PV is kept in BB's cache. So, if you can grok Python, patches are
welcome (or if you don't, there're yet few weeks before the OE bugday
;-) ).

[]

-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com