[Openembedded-users] overlay questions

[Yusuf Caglar AKYUZ]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anthony Tzouris wrote:
> If I use the /stuff/build directory then I cannot avoid having a single
> build directory for all overlays.  My intent is to have different
> workspaces (overlays) and a pristine (unmodified) /stuff build directory.
> 

I don't think this is how overlays work. My understanding of
overlays and general OE workflow is this:

There are recipes(packages) + config files for machines + config
files for distros in main OE repository. If you want to override
anything from this repo or to add new recipes, you create an
overlay. In this way you only change parts related to your specific
needs, use your own source control for your internal development. So
when you sync your OE tree with upstream, your changes are not lost.
You may have multiple overlays, so that multiple levels of recipe
overrides.

Recipes are built into different categories including recipes common
to all architectures, architecture specific recipes and machine
specific recipes. There is also a host related directory. This way
build directories are shared as much as possible. These are not
related to overlays. Overlays do not define what goes to where, they
define what comes from where.

So there are 2 ways for you as far as I am concerned:

1) You should define different machine names in your different
   overlays so that your each overlay will have its own directory
   and still use much of the common builds.

2) While creating recipes in your overlays, suffix(or prefix) *.bb
   files distinctively so that they end up in different build
   directories. Though this will not work if recipes are providing
   libraries, but they will have different opkg packages for sure
   provided that recipes are using $PN variable instead of
   hard-coding names.

Just my 0.02 cents...

Regards,
Caglar



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkoxRfQACgkQ/nL+S5dojeg4BQCeObKfTWhhRb8PoHJH0HfYmgK5
7IMAn2uwvVH06AeOTr1ccllRnqXjfjko
=MuRN
-----END PGP SIGNATURE-----