some trivial questions on building angstrom image for BB

i'm putting together my presentation on the BB for next week's local
linux fest, and part of the talk will be on building angstrom for the
BB, so some simple questions that i actually think i know the answers
to but i just want to be sure:

1) any problems with using the org.openembedded.dev branch for the
build? i've mostly used the stable/2009 branch but i figure i might
as well live dangerously since it's just a talk. is there any reason
i *shouldn't* use the dev branch?

2) we had this discussion before and i'm not sure how it ended, but i
noticed some time ago that the stable branch of OE contains bitbake
while the dev branch doesn't. this means that if you've been building
with stable/2009 and suddenly checkout the dev branch, the build will
most likely fail unless you've installed bitbake yourself. i'm going
to test that again right away but for people who've done this, is
there any restriction on where i install bitbake as long as it's in my
search path?

  and that's about it. granted, the above questions are really OE
questions, but i wanted to ask BB people just to make sure it was
applicable to my situation. thanks muchly.

rday

i'm putting together my presentation on the BB for next week's local
linux fest, and part of the talk will be on building angstrom for the
BB, so some simple questions that i actually think i know the answers
to but i just want to be sure:

1) any problems with using the org.openembedded.dev branch for the
build? i've mostly used the stable/2009 branch but i figure i might
as well live dangerously since it's just a talk. is there any reason
i *shouldn't* use the dev branch?

Sometimes, that is why it is called living dangerously :slight_smile:

2) we had this discussion before and i'm not sure how it ended, but i
noticed some time ago that the stable branch of OE contains bitbake
while the dev branch doesn't. this means that if you've been building
with stable/2009 and suddenly checkout the dev branch, the build will
most likely fail unless you've installed bitbake yourself. i'm going
to test that again right away but for people who've done this, is
there any restriction on where i install bitbake as long as it's in my
search path?

Just make sure the correct version is in your path. You will also need
a separate tmp directory for .dev. It would be useful having a set of
instructions on setting up a build environment where you could easily
switch between the two branches,

Not that we need more set of instructions ...

Philip

> 2) we had this discussion before and i'm not sure how it ended,
> but i noticed some time ago that the stable branch of OE contains
> bitbake while the dev branch doesn't. this means that if you've
> been building with stable/2009 and suddenly checkout the dev
> branch, the build will most likely fail unless you've installed
> bitbake yourself. i'm going to test that again right away but for
> people who've done this, is there any restriction on where i
> install bitbake as long as it's in my search path?

Just make sure the correct version is in your path. You will also
need a separate tmp directory for .dev.

  i'm assuming you mean that i simply can't share the TMPDIR
(angstrom-dev, in my case) between those two builds. which i had
already assumed.

It would be useful having a set of instructions on setting up a
build environment where you could easily switch between the two
branches,

  what i did was unload the bitbake-1.8.12 tarball under my home
directory, and add it to the PATH. now, when i use the stable/2009
branch, bitbake is found under openembedded. when i switch to the
.dev branch, bitbake is picked up from my home dir. no problem. a
little counter-intuitive, but easily done. both versions are 1.8.12.

rday