[Angstrom-devel] RFC: feed population policy

[Joshua Layne]

On Mon, 12 Nov 2007 23:32:19 +0100, "Clement Hermann (nodens)"
<clement.hermann at free.fr> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Joshua Layne a écrit :
>> Does the rm_work option require a full rebuild every time you build?
>> Unfortunately, that takes several days on my current system (a day and a
>> half if nothing goes wrong, longer if I need to manually help the
>> process)  One of the primary reasons that I have set up OE is to allow
>> me to build other packages that I am interested in and have them neatly
>> packaged up into ipk's - it seems like this requires a persistent work
>> environment, but I may not understand it properly.
>>
>> Thanks for the tip on this - it is quite likely that I am missing a few
>> optimizations on my environment.
>>
> 
> rm_work cleans up the work directory. The staging directory, where the
> builded binaries are stored, as well as the stamp directory (which, as I
> understand it, tells OE what needs not to be done) remains untouched. So
> even if you use rm_work, you won't have to rebuild everything each time
> you need a single package (or it wouldn't be very useful...).

Thanks for the reply - I am still not clear on whether it can handle
multiple build targets with different version masks.

For example, gpe-phone requires GTK+ 2.6, Angstrom defaults to GTK+ 2.10 -
if I build a package for gpe-phone (htctornado) that shares a build
directory with angstrom (h2200), will it be built against 2.6 or 2.10? -
how can I tell the difference in the resultant package?  They seem to be
named off the bitbake recipe, not off the required libraries.

The way I am currently handling it is to have two totally separate build
directories, but I am therefore duplicating a lot of effort and hard disk
space.

Finally, does anyone have a local.conf with an example of rm_work - I have
not found a good reference for this.

Thanks all,
josh