The only way this could be fixed is to remove the aforementioned guidelines.. Like I said, there are plenty of examples in the code. Those packageconfigs where elaborated based on: 1. if a package has support for both BlueZ versions; 2. If not, usually only BlueZ 4 is supported;
Care to elaborate how I can fix them otherwise? I am open to suggestions. Thanks, Cristian -----Original Message----- From: Tanu Kaskinen [mailto:[email protected]] Sent: Tuesday, April 7, 2015 2:41 PM To: Iorga, Cristian Cc: [email protected] Subject: Re: [OE-core] [PATCH 5/5] bluetooth.bbclass: set bluez5 as the default BT stack On Tue, 2015-04-07 at 11:23 +0000, Iorga, Cristian wrote: > The aforementioned packageconfigs are just examples/guidelines, we > added code for diverse recipes on a case by case scenario. My point was that the examples/guidelines are misleading, and should be fixed. -- Tanu -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
