[oe] How to best handle different build configurations (local.conf)?

[Paul Menzel]

Dear OE hackers,


I imagine you juggle with different configurations for BitBake day in,
day out to specify different compiler versions or to build different
distributions. Could you please tell me what proofed to be the best
approach?

My requirements are that rebuilding everything should be avoided and
space should not be wasted.

I am using the setup described for Ångström [1] (local.conf [2]).

If I understood that correctly `local.conf` is the place where all this
happens.

Reading `bitbake -h` I did not find an option to specify a path to
`local.conf`.

In the `source-me.txt` [3] from [1] `PKGDIR` gets set to
`{OETREE}/build/` which is entered later on, but I could neither find a
reference for it in the BitBake user manual nor in the OE repository. So
it must be specific to this script.

To save the already build files for other platforms one should change
`TMPDIR` to a separate directory for each config.

        # Set TMPDIR instead of defaulting it to $pwd/tmp
        TMPDIR = "${OETREE}/${DISTRO}-dev"

1. So is the solution to have a directory with an adapted
`conf/local.conf` below which one enters before building a different
configuration?
2. Is there advantage to but this in a separate Git repository and
switch the branch to build a different configuration?
3. Or do you just set the environment variables yourself?

That is not so much work, but if you do it regularly pretty bothersome.


Thanks,

Paul


[1] http://www.angstrom-distribution.org/building-angstrom
[2] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/contrib/angstrom/local.conf
[3] http://www.angstrom-distribution.org/files/source-me.txt
[4] http://bitbake.berlios.de/manual/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20100123/25805c6b/attachment-0002.sig>