From: Kent Gibson <warthog618@gmail.com>
To: Seamus de Mora <seamusdemora@gmail.com>
Cc: linux-gpio@vger.kernel.org
Subject: Re: [libgpiod] help with GPIOSET_INTERACTIVE
Date: Sat, 30 Dec 2023 10:21:36 +0800 [thread overview]
Message-ID: <20231230022136.GA19799@rigel> (raw)
In-Reply-To: <CAJ8C1XP2xeTRvJRpvmd8VD4RGYQTH4qWQdMocmNVgRWkmSDscQ@mail.gmail.com>
On Fri, Dec 29, 2023 at 07:50:21PM -0600, Seamus de Mora wrote:
> On Fri, Dec 29, 2023 at 9:58 AM Kent Gibson <warthog618@gmail.com> wrote:
> >
>
> > This works for me on a Pi, both bullseye and bookworm:
> >
> > $ ./autogen.sh --enable-tools --enable-gpioset-interactive
> > $ make
>
> That option ('--enable-gpioset-interactive') seems to have gotten the
> job done. I had to back out of 'libgpiod-2.1/tools' to
> '~/libgpiod-2.1', and let './autogen.sh' take care of the '#define'...
> instead of me trying to add it manually to 'gpioset.c' via '#define
> GPIOSET_INTERACTIVE'. I do have **all** the packages you listed below
> installed, so why my manual addition didn't work is still a mystery to
> me - but not one worth fretting over.
>
If you want to change build options then you need to re-run autogen.sh to
regenerate the Makefiles.
The option is mentioned in both TOOLS section of the README (but I note
has a typo that needs to be fixed) adjacent to the interactive example,
and the configure help, which is itself mentioned in the README:
$ ./configure --help
...
--enable-gpioset-interactive
enable gpioset interactive mode [default=no]
...
That is not enabled by default as some platforms lack, or want to avoid
including, libedit.
> > That is with the following packages installed:
> > autoconf
> > autoconf-archive
> > libtool
> > m4
> > libedit-dev
>
> Thanks for your help! :)
And thank you for the SE un-upvote and downvote!
Cheers,
Kent.
next prev parent reply other threads:[~2023-12-30 2:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 9:14 help with GPIOSET_INTERACTIVE Seamus de Mora
2023-12-29 15:58 ` [libgpiod] " Kent Gibson
2023-12-30 1:50 ` Seamus de Mora
2023-12-30 2:21 ` Kent Gibson [this message]
2023-12-30 4:43 ` Seamus de Mora
2023-12-30 5:03 ` Kent Gibson
2023-12-30 5:45 ` Seamus de Mora
2023-12-30 5:53 ` Kent Gibson
2023-12-30 6:25 ` Seamus de Mora
2023-12-30 6:29 ` Kent Gibson
2023-12-30 6:36 ` Seamus de Mora
2023-12-30 6:43 ` Kent Gibson
2023-12-30 6:49 ` Seamus de Mora
2023-12-30 6:51 ` Kent Gibson
2023-12-30 6:56 ` Seamus de Mora
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231230022136.GA19799@rigel \
--to=warthog618@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=seamusdemora@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox