[oe] CALL FOR ACTION: get rid of native recipes
Denys Dmytriyenko
denis at denix.org
Wed Aug 4 00:03:05 UTC 2010
On Tue, Aug 03, 2010 at 03:58:15PM +0200, Dr. Michael Lauer wrote:
> Am 03.08.2010 um 14:46 schrieb Richard Purdie:
>
> > On Tue, 2010-08-03 at 10:21 +0200, Dr. Michael Lauer wrote:
> >> that's pretty cool, however I think we should restrict this list
> >> to those recipes which also have a non-native variant.
> >>
> >> E.g. the 2nd entry in this list is android-image-utils-native for
> >> which a non-native variant makes little sense.
> >
> > Just to add, there are some cases where the -native recipe still makes
> > sense as the alternative is rather ugly for example, python-native,
> > perl-native and a handful of others. The number of these cases is
> > extremely small however. BBCLASSEXTEND makes sense in most cases.
>
> Oh right, the recipes for those pesky scripting languages are quite finnicky,
> so I would prefer to not change them unless absolutely necessary :)
Yeah, that was also mentioned in Frans' original email... :) Here:
> - in some cases: leave as is (e.g. if it is only a native recipe, or if it
> is very difficult to convert)
--
Denys
More information about the Openembedded-devel
mailing list