[oe] [meta-oe][PATCH 0/6] sigrok: set of new packages

[Bartosz Golaszewski]

niedz., 25 lis 2018 o 16:40 Nathan Rossi <nathan at nathanrossi.com> napisał(a):
>
> On Mon, 26 Nov 2018 at 01:12, Bartosz Golaszewski <brgl at bgdev.pl> wrote:
> >
> > niedz., 25 lis 2018 o 07:04 Nathan Rossi <nathan at nathanrossi.com> napisał(a):
> > >
> > > On Sat, 24 Nov 2018 at 01:39, Bartosz Golaszewski <brgl at bgdev.pl> wrote:
> > > >
> > > > This series adds recipes for libsigrok and accompanying libraries and
> > > > tools. The eventual goal is to add pulseview - the graphical interface
> > > > for sigrok - to meta-qt5-extra.
> > > >
> > > > First two patches add external packages used by libsigrok. The third
> > > > patch adds a recipe for native doxygen, which is needed to generate
> > > > libsigrok C++ bindings which will in turn be necessary to build
> > > > pulseview.
> > > >
> > > > Last three patches add recipes for the sigrok suite including the
> > > > command-line utility - sigrok-cli.
> > > >
> > > > Bartosz Golaszewski (6):
> > > >   libzip: new package
> > > >   libserialport: new package
> > > >   doxygen: new native package
> > > >   libsigrok: new package
> > > >   libsigrokdecode: new package
> > > >   sigrok-cli: new package
> > >
> > > Anything against marking all the recipes (excluding doxygen) with
> > > BBCLASSEXTEND = "native nativesdk"?
> > >
> >
> > What would be the reason for that? Also: you'd need to do that for ALL
> > non-direct sigrok dependencies and I think there are quite a few.
>
> It makes it really easy to ship with a nativesdk toolset or use on
> your build host. I have personally been using it this way and made
> some recipes for it a few months ago
> (https://github.com/nathanrossi/meta-random/tree/master/recipes-toolbox/sigrok).
>
> With the recipes in this series the only dependency that is not also
> enabled for native/nativesdk is glibmm. However that is not enabled by
> default (since its a dependency of 'cxx' config).
>

I guess it can always be added later on. I'll stick to target packages for now.

> >
> > > Also any plans to include recipes for any of the firmware data
> > > packages that sigrok provides? (e.g. sigrok-firmware-fx2lafw)
> > >
> >
> > I don't personally need it and it seems like it requires integrating
> > the sdcc compiler into yocto. Probably more work than I can spend on
> > that.
>
> I was only referring to the pre-built firmware binaries that are
> released by the sigrok project.
> https://sigrok.org/download/binary/sigrok-firmware-fx2lafw/.
>

Same as above, no problem adding it later.

Bart