Paul Eggleton writes:
>> >> 1. set some defaults on distribution base ...
>> >> 2. allow to override these defaults on a per-project base
fwiw, I am using now
_EXT_PROJECT_FEATURES = "\
largefile nfsroot modules ld-is-gold ${PROJECT_FEATURES} \
${DISTRO_FEATURES_INITMAN} ${DISTRO_FEATURES_L
On Monday 28 January 2013 17:23:40 Enrico Scholz wrote:
> Paul Eggleton writes:
> >> 1. set some defaults on distribution base ...
> >> 2. allow to override these defaults on a per-project base
> >> ...
> >> afaik, DISTRO_FEATURES_BACKFILL + _CONSIDERED exist to allow the first
> >> two point with
Paul Eggleton writes:
>> 1. set some defaults on distribution base ...
>> 2. allow to override these defaults on a per-project base
>> ...
>> afaik, DISTRO_FEATURES_BACKFILL + _CONSIDERED exist to allow the first
>> two point without an '-=' operator which lacks in bitbake.
>
> No they don't. The
On Mon, 2013-01-28 at 16:44 +0100, Enrico Scholz wrote:
> afaik, DISTRO_FEATURES_BACKFILL + _CONSIDERED exist to allow the first
> two point without an '-=' operator which lacks in bitbake.
That wasn't really the intention. The original purpose of
DISTRO_FEATURES_BACKFILL was to allow behaviour t
On Monday 28 January 2013 16:44:15 Enrico Scholz wrote:
> Phil Blundell writes:
> > This does seem rather like an abuse of DISTRO_FEATURES_BACKFILL. Can
> > you explain why you are doing it this way rather than just setting
> > DISTRO_FEATURES directly to what you wanted?
>
> I need a way to:
>
Phil Blundell writes:
> This does seem rather like an abuse of DISTRO_FEATURES_BACKFILL. Can
> you explain why you are doing it this way rather than just setting
> DISTRO_FEATURES directly to what you wanted?
I need a way to:
1. set some defaults on distribution base and avoid nasty details li
On Mon, 2013-01-28 at 15:52 +0100, Enrico Scholz wrote:
> There are some implicit relations between features (e.g. when selecting
> 'usbhost' I *usually* want 'vfat' or 'ext2' support too). So I have
>
> DISTRO_FEATURES_BACKFILL = "\
> largefile nfsroot modules ld-is-gold ${PROJECT_FEATURES}
Paul Eggleton writes:
> Why are you assigning *_FEATURES_BACKFILL at all?
There are some implicit relations between features (e.g. when selecting
'usbhost' I *usually* want 'vfat' or 'ext2' support too). So I have
DISTRO_FEATURES_BACKFILL = "\
largefile nfsroot modules ld-is-gold ${PROJEC
On Monday 28 January 2013 14:55:05 Enrico Scholz wrote:
> Richard Purdie writes:
> >> > Backfilling DISTRO_FEATURES and MACHINE_FEATURES with _append
> >> > statements
> >> > happens too late to use those variables with conditional inherits, like
> >>
> >> > this:
> >> This causes regressions for
Richard Purdie writes:
>> > Backfilling DISTRO_FEATURES and MACHINE_FEATURES with _append statements
>> > happens too late to use those variables with conditional inherits, like
>> > this:
>>
>> This causes regressions for setups where DISTRO_FEATURES_BACKFILL uses
>> the override mechanism. E.g
On Fri, 2013-01-25 at 19:06 +0100, Enrico Scholz wrote:
> Ross Burton
> writes:
>
> > Backfilling DISTRO_FEATURES and MACHINE_FEATURES with _append statements
> > happens too late to use those variables with conditional inherits, like
> > this:
>
> This causes regressions for setups where DISTRO
Ross Burton
writes:
> Backfilling DISTRO_FEATURES and MACHINE_FEATURES with _append statements
> happens too late to use those variables with conditional inherits, like
> this:
This causes regressions for setups where DISTRO_FEATURES_BACKFILL uses
the override mechanism. E.g. I have
| DISTRO_FE
From: Richard Purdie
Backfilling DISTRO_FEATURES and MACHINE_FEATURES with _append statements happens
too late to use those variables with conditional inherits, like this:
inherit ${@base_contains('DISTRO_FEATURES','sysvinit','update-rc.d_real','',d)}
Instead, do the backfilling at ConfigParse
13 matches
Mail list logo
