[oe] [meta-oe][PATCH] libgpiod: bump version to v1.3

Khem Raj raj.khem at gmail.com
Thu Mar 28 13:49:16 UTC 2019


On Thu, Mar 28, 2019 at 3:29 AM Bartosz Golaszewski <brgl at bgdev.pl> wrote:

> pon., 25 mar 2019 o 18:30 Khem Raj <raj.khem at gmail.com> napisał(a):
> >
> > On Mon, Mar 25, 2019 at 7:26 AM Bartosz Golaszewski
> > <bgolaszewski at baylibre.com> wrote:
> > >
> > > pon., 25 mar 2019 o 15:19 Khem Raj <raj.khem at gmail.com> napisał(a):
> > > >
> > > >
> > > >
> > > > On Mon, Mar 25, 2019 at 7:05 AM Bartosz Golaszewski <brgl at bgdev.pl>
> wrote:
> > > >>
> > > >> From: Bartosz Golaszewski <bgolaszewski at baylibre.com>
> > > >>
> > > >> There are several new features in this release. The one that impacts
> > > >> the recipe is the option to install the test executable to bindir
> using
> > > >> the new options (--enable-install-tests). This requires separate
> > > >> PACKAGECONFIG entries for 0.x and 1.x series.
> > > >
> > > >
> > > > Perhaps it will be good to enable this feature automatically when
> ptest is enabled via distro features
> > > >>
> > >
> > > Sure, how about a separate patch I'll send later this week?
> >
> > okay that works too
>
> A question about that: the testing framework for libgpiod requires a
> specific kernel module to be built (the gpio-mockup testing driver).
> How should I go about depending on it? I couldn't find any example of
> that.
>

There is no given way for tethering the kernel config logic and warn or
errror about that elegantly
May be a kernel config parser in bitbake could be a nice feature

>
> Bart
>


More information about the Openembedded-devel mailing list