From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] pigpio: new package
Date: Tue, 9 Oct 2018 15:37:10 +0200 [thread overview]
Message-ID: <20181009153710.1b016af2@windsurf> (raw)
In-Reply-To: <20180928180034.6543-1-grzegorz@blach.pl>
Hello,
On Fri, 28 Sep 2018 20:00:33 +0200, Grzegorz Blach wrote:
> Pigpio is a library for the Raspberry Pi which allows
> control of the General Purpose Input Outputs (GPIO).
>
> http://abyz.me.uk/rpi/pigpio/
>
> Signed-off-by: Grzegorz Blach <grzegorz@blach.pl>
> ---
> DEVELOPERS | 1 +
> package/Config.in | 1 +
> package/pigpio/Config.in | 8 ++++++++
> package/pigpio/pigpio.hash | 3 +++
> package/pigpio/pigpio.mk | 25 +++++++++++++++++++++++++
> 5 files changed, 38 insertions(+)
> create mode 100644 package/pigpio/Config.in
> create mode 100644 package/pigpio/pigpio.hash
> create mode 100644 package/pigpio/pigpio.mk
I really wonder how many RaspberryPi-specific libraries/programs to
toggle GPIOs will be needed before people discover the standard Linux
interfaces to manipulate GPIOs.
Anyway, I've applied, with the following changes:
[Thomas:
- Use proper SPDX tag for The Unlicense
- Add missing dependency on !BR2_STATIC_LIBS, since the Makefile is
unconditionally building a shared library
- Use BR2_arm instead of BR2_ARM_EABIHF, there's nothing that makes
it EABIHF specific.
- Use -D and full destination paths during the installation.]
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-10-09 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 18:00 [Buildroot] [PATCH 1/2] pigpio: new package Grzegorz Blach
2018-09-28 18:00 ` [Buildroot] [PATCH 2/2] python-pigpio: " Grzegorz Blach
2018-10-09 13:40 ` Thomas Petazzoni
2018-10-09 13:37 ` Thomas Petazzoni [this message]
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=20181009153710.1b016af2@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.