From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] Add package hackrf-tools
Date: Sun, 11 Oct 2015 11:18:20 +0200 [thread overview]
Message-ID: <20151011111820.21f6a115@free-electrons.com> (raw)
In-Reply-To: <1444546853-1505-2-git-send-email-jrspruitt@gmail.com>
Dear Jason Pruitt,
On Sun, 11 Oct 2015 00:00:53 -0700, Jason Pruitt wrote:
> diff --git a/package/hackrf-tools/Config.in b/package/hackrf-tools/Config.in
> new file mode 100644
> index 0000000..71fced6
> --- /dev/null
> +++ b/package/hackrf-tools/Config.in
> @@ -0,0 +1,8 @@
> +config BR2_PACKAGE_HACKRF_TOOLS
> + bool "hackrf-tools"
> + depends on BR2_PACKAGE_LIBHACKRF && (BR2_SHARED_STATIC_LIBS || BR2_SHARED_LIBS)
Improper indentation. Besides that, if something doesn't build with
pure static libraries, we normally do:
depends on !BR2_STATIC_LIBS
and add a comment:
comment "hackrf-tools needs a toolchain w/ dynamic library"
depends on BR2_STATIC_LIBS
Regarding the "depends on BR2_PACKAGE_LIBHACKRF", it should be a
"select" instead:
select BR2_PACKAGE_LIBHACKRF
and then you need to propagate the reverse dependencies of libhackrf:
depends on BR2_TOOLCHAIN_HAS_THREADS
and of course keep a comment about this thread dependency. So the
comment above should in fact be:
comment "hackrf-tools needs a toolchain w/ threads, dynamic library"
depends on BR2_STATIC_LIBS || !BR2_TOOLCHAIN_HAS_THREADS
However, this is all moot if you merge both packages into one, as
suggested in my review of the libhackrf package.
> + help
> + Tools for interacting with and updating HackRF boards.
> +
> + https://github.com/mossmann/hackrf/host/hackrf-tools
> +
Unneeded empty new line.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-10-11 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 7:00 [Buildroot] [PATCH 1/2] Add package libhackrf Jason Pruitt
2015-10-11 7:00 ` [Buildroot] [PATCH 2/2] Add package hackrf-tools Jason Pruitt
2015-10-11 8:12 ` Samuel Martin
2015-10-11 9:18 ` Thomas Petazzoni [this message]
2015-10-11 8:17 ` [Buildroot] [PATCH 1/2] Add package libhackrf Samuel Martin
2015-10-11 9:15 ` Thomas Petazzoni
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=20151011111820.21f6a115@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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