Re: [yocto] gpsd [version 3.23; master branch]: Is it possible to include / enable ubxtool?

2021-09-01 Thread Peter Bergin
Hi Matthias, On 2021-09-01 17:11, Matthias Klein wrote: Hello Peter, I'm not sure it's that simple. Sorry for my quick and a bit oversimplified response. I did my first build on an older version (3.20) where ubxtool was not built but present in the repo root. I see now that in 3.23 gpsd have

Re: [yocto] gpsd [version 3.23; master branch]: Is it possible to include / enable ubxtool?

2021-09-01 Thread Matthias Klein
Betreff: Re: [yocto] gpsd [version 3.23; master branch]: Is it possible to include / enable ubxtool? Hi Matthias, On 2021-09-01 12:33, Matthias Klein wrote: > Hello, > > is it somehow possible to add the ubxtool in the gpsd-utils package? > > (I use the current master branch) > gpsd

Re: [yocto] gpsd [version 3.23; master branch]: Is it possible to include / enable ubxtool?

2021-09-01 Thread Peter Bergin
Hi Matthias, On 2021-09-01 12:33, Matthias Klein wrote: Hello, is it somehow possible to add the ubxtool in the gpsd-utils package? (I use the current master branch) gpsd recipe is located in meta-oe. As the ubxtool file is present in the build it is possible to add it. Just make sure it is

Re: [yocto] gpsd [version 3.23; master branch]: Is it possible to include / enable ubxtool?

2021-09-01 Thread Zoran
To add every package (into poky) by every personal wish of any Yocto user, or not to add any package without exclusion, that is the question? Why not to do addition of the proprietary layer for missing package or group of missing by the same/similar context packages??? Zee ___ On Wed, Sep

[yocto] gpsd [version 3.23; master branch]: Is it possible to include / enable ubxtool?

2021-09-01 Thread Matthias Klein
Hello, is it somehow possible to add the ubxtool in the gpsd-utils package? (I use the current master branch) Best regards, Matthias -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#54625): https://lists.yoctoproject.org/g/yocto/message/54625