[oe] Using 'mr' to manage an oe-core build environment (configuration and layers)

[Antonio Ospite]

Hi,

I was looking into 'mr'[1] for another project and I thought about
trying it for an oe-core workflow.

The idea is to manage layers and configurations to set up a certain
build environment with as few files as possible and with a way to easily
recreate that environment, I've heard about alternative ways of doing
that using 'repo' from android or git submodules, or some OE specific
scripts, but I don't really know the details of those and I am not able
to compare them with my approach, so I thought I'd just share it here
and let you tell me.

Here is some brief documentation:
http://ao2.it/tmp/oe-ezx-build/README.asciidoc

You can recreate the build environment with just this command:
  mr bootstrap http://ao2.it/tmp/oe-ezx-build/.mrconfig oe-ezx-build

This will bring in the configuration for the build environment (kept
under revision control as well as the .mrconfig itself), and will
checkout all the needed layers.

You can start building right away with:
  cd oe-ezx-build
  . ./oe-core/oe-init-build-env
  bitbake meta-toolchain

You can do some work in the various component of the environment and
check the status with:
  mr status

BTW the output of this last command makes me wonder if oe-core should
put bitbake/ in .gitignore

Adding layers is not immediate yet because this is a rare event in my
use case.

Final note, the repository under http://ao2.it/tmp/ is temporary and
will most likely go away sometimes in the future. :)

Thanks,
   Antonio

[1] http://kitenet.net/~joey/code/mr/

-- 
Antonio Ospite
http://ao2.it

PGP public key ID: 0x4553B001

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20111209/c625ddf2/attachment-0002.sig>