[oe] [Angstrom-devel] [RFC] Per-ANGSTROM_MODE caches for Angstrom

[Paul Sokolovsky]

Hello,


So, no objections? I'll add it then, and RFC adding to stable branch
too. I'd like to keep that extra check for ANGSTROM_MODE being set - it
at least consistent with existing MACHINE check.


On Sat, 16 Feb 2008 17:52:42 +0200
Paul Sokolovsky <pmiscml at gmail.com> wrote:

[]
> > > It's pretty annoying to wait for cache rebuild each time
> > > ANGSTROM_MODE is swicthed, especially if that happens often.
> > > Following patch stores bitbake cache for each mode separately:
> > >
> > > #
> > > # old_revision [1821f6eadefc14ad7ce51d5ab026da139608f557]
> > > #
> > > # patch "conf/distro/include/angstrom.inc"
> > > #  from [b86b952c90304d1fd39f1415f6af7f71d02e00df]
> > > #    to [e7921869d30b7e5df3fd39fbd4bec5d2495b5d31]
> > > #
> > > ============================================================
> > > --- conf/distro/include/angstrom.inc
> > > b86b952c90304d1fd39f1415f6af7f71d02e00df +++
> > > conf/distro/include/angstrom.inc
> > > e7921869d30b7e5df3fd39fbd4bec5d2495b5d31 @@ -12,6 +12,7 @@
> > > ANGSTROM_MODE ?= "glibc" # Can be "glibc", "eglibc" or "uclibc"
> > > ANGSTROM_MODE ?= "glibc"
> > >
> > > +CACHE = "${TMPDIR}/cache${@['', '/' +
> > > str(bb.data.getVar('ANGSTROM_MODE', d,
> > > 1))][bool(bb.data.getVar('ANGSTROM_MODE', d, 1))]}${@['', '/' +
> > > str(bb.data.getVar('MACHINE', d,
> > > 1))][bool(bb.data.getVar('MACHINE', d, 1))]}" DEPLOY_DIR =
> > > "${TMPDIR}/deploy/${ANGSTROM_MODE}" require
> > > conf/distro/include/angstrom-${ANGSTROM_MODE}.inc
> > 
> > +1, for the  idea, but why not just
> > ${TMPDIR}/cache/${ANGSTROM_MODE} ?
> 
> Well, nice question ;-). To be generic and putable even in
> bitbake.conf ;-)
> 
> > And I don't understand why you need to include MACHINE there.
> > I've never needed to rebuild caches when switching MACHINE, and I
> > shouldn't have to.
> 
> Heh, multimachine puts it there ;-)
> 
> > 
> > regards
> > Philipp
> 
> 
> -- 
> Best regards,
>  Paul                          mailto:pmiscml at gmail.com



-- 
Best regards,
 Paul                          mailto:pmiscml at gmail.com