On Tue, Mar 3, 2020 at 4:32 AM Peter Kjellerstedt < peter.kjellerst...@axis.com> wrote:
> > -----Original Message----- > > From: openembedded-core-boun...@lists.openembedded.org > <openembedded-core- > > boun...@lists.openembedded.org> On Behalf Of rpj...@crashcourse.ca > > Sent: den 2 mars 2020 13:41 > > To: openembedded-core@lists.openembedded.org > > Subject: [OE-core] how to cleanly centralize a zillion BBCLASSEXTEND += > > "nativesdk" settings? > > > > layer i'm currently perusing has many, many bbappend files, of which > > quite a number are nothing more than the single line: > > > > BBCLASSEXTEND += "nativesdk" > > > > literally, at least a hundred append files are like that. so rather > > than clutter up the layer with all those trivial .bbappend files, > > can one cram all that into a single .conf file? as i read it, can i > > do something like: > > > > BBCLASSEXTEND_append_pn-pkg1 = " nativesdk" > > BBCLASSEXTEND_append_pn-pkg2 = " nativesdk" > > ... and on and on ... > > > > and toss all that into a distro.conf file or something? > > > > and even if that works, is it considered good coding style? > > > > rday > > Sounds perfectly fine. We do something similar, but in our case we need > to add "native" to BBCLASSEXTEND for a whole bunch of recipes. > Should patches be sent to add native and nativesdk? Drop the technical debt by upstreaming... > > //Peter > > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core >
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
