I was just going to make a package for this for myself, but now I'm wondering if it shouldn't be in the main slackwarearm-current tree

If you don't know, libgpiod is a C/C++/Python3 library and some tools for working with the new /dev/gpiochip* interface for the GPIO pins on many ARM boards. Seeing as to how the sysfs interface is depreciated and may disappear in the future, I think it would be a good idea to get this package in -current

I built myself a quick and dirty test package on my Pi 4 on -current. I haven't done much more than blink a few LEDs, but everything seems to work. I tired Python, C, and the tools. Here's the configure options I used
The source code for releases is here. I used the 1.6.2 version

Thoughts? The tools are the main reason I think it should be included, similar to i2c-tools, but it doesn't hurt to have the libs. On the flip side, probably not many people use GPIO

Very interesting, I'll have to append it to my to do (look at) list. What kerenel version were you running when you compiled?

5.10.14-v7l-sarpi4

I have just set up a raspberry pi zero, installed libgpiod and had a quick squiz. It seems the gpiod commands are to be used for (bash) scripting now that GPIO sysfs is to be depreciated post linux 4.8. I've been using wiringpPi in C programs on my bananapros to interface with gpio pins and probably will on this rpi zero as well. Might be good to include it in future Slackwarearm but unless I'm unable to, I'll stick with wiringpi and C.

Additions to the main Slackware distribution are only when they are absolutely required.
I'll look at adding it to /extra.

I think it would be great to include libgpiod as part of the slackwarearm project. Using the gpio's on any single board computer opens a whole new universe of projects. I've done one Hackerpublicradio episode on a pi, running slackware, I use in my house to monitor a basement sump. In the process of putting that project together I found pigpio, at http://abyz.me.uk/rpi/pigpio/pigpiod.html, to do the heavy lifting, more robust and still maintained, unlike wiringpi. But I'd rather see libgpiod as part of slackware arm.

1 members found this post helpful.

Hm, I didn't even think of putting it in /extra but that's a good option. People who need it now will still have it available and you can easily move it into the main tree if it becomes a requirement for something. I believe that's a better option than having it on slackbuilds.org when 15 comes out

I concur, extra is a great place for it, not slackbuilds.

I did not realise Gordon had given it away, I just read his post. I suppose I'll have to start using gpiod In my C programs .... very timely with a birthday next week .... will have to work a little more harder at keeping the brain matter in shape again.

This is now in /extra for -current. I will look at moving it to the main tree once 15.0's released.

2 members found this post helpful.