From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/brickd: new package
Date: Tue, 26 Mar 2019 22:26:47 +0100 [thread overview]
Message-ID: <20190326222647.3f33146a@windsurf> (raw)
In-Reply-To: <20190223010454.7335-1-david@lechnology.com>
On Fri, 22 Feb 2019 19:04:53 -0600
David Lechner <david@lechnology.com> wrote:
> This adds a new package for brickd. Brickd is system management daemon
> for the LEGO MINDSTORMS EV3 programmable brick.
>
> Signed-off-by: David Lechner <david@lechnology.com>
I've applied, after fixing one dependency issue, see below.
> diff --git a/package/brickd/Config.in b/package/brickd/Config.in
> new file mode 100644
> index 0000000000..bd62e15122
> --- /dev/null
> +++ b/package/brickd/Config.in
> @@ -0,0 +1,17 @@
> +config BR2_PACKAGE_BRICKD
> + bool "brickd"
> + depends on BR2_PACKAGE_HAS_UDEV # gudev
> + depends on BR2_TOOLCHAIN_HAS_THREADS # glib2
> + depends on BR2_USE_WCHAR # glib2
> + select BR2_PACKAGE_LIBGLIB2
> + select BR2_PACKAGE_LIBGUDEV
Both libglib2 and libgudev have a depends on BR2_USE_MMU, so it should
have been replicated here.
> + help
> + Brick daemon for LEGO MINDSTORMS EV3 (and other LEGO-
> + compatible devices). This performs tasks like battery
> + management and controls device-specific hardware.
> +
> + https://github.com/ev3dev/brickd
> +
> +comment "brickd needs udev /dev management, a toolchain w/ threads, wchar"
> + depends on !BR2_PACKAGE_HAS_UDEV || !BR2_TOOLCHAIN_HAS_THREADS || \
> + !BR2_USE_WCHAR
And here.
I said, I fixed that up when applying.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-03-26 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 1:04 [Buildroot] [PATCH 1/2] package/brickd: new package David Lechner
2019-02-23 1:04 ` [Buildroot] [PATCH 2/2] configs/lego_ev3_defconfig: enable brickd by default David Lechner
2019-03-26 21:26 ` Thomas Petazzoni
2019-03-26 21:26 ` 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=20190326222647.3f33146a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox