All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin Böh via buildroot" <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: "Martin Böh" <contact@martb.dev>,
	"Gwenhael Goavec-Merou" <gwenhael.goavec-merou@trabucayre.com>
Subject: [Buildroot] [PATCH 1/1] package/gr-osmosdr: add support for HACKRF receivers
Date: Thu, 23 Feb 2023 21:18:17 +0100	[thread overview]
Message-ID: <20230223201817.224238-1-contact@martb.dev> (raw)

Signed-off-by: Martin Böh <contact@martb.dev>
---
 package/gr-osmosdr/Config.in     | 6 ++++++
 package/gr-osmosdr/gr-osmosdr.mk | 7 +++++++
 2 files changed, 13 insertions(+)

diff --git a/package/gr-osmosdr/Config.in b/package/gr-osmosdr/Config.in
index 04fa10be80..05b5c46a63 100644
--- a/package/gr-osmosdr/Config.in
+++ b/package/gr-osmosdr/Config.in
@@ -43,4 +43,10 @@ config BR2_PACKAGE_GR_OSMOSDR_RFSPACE
 	help
 	  Enable RFSPACE Receivers support
 
+config BR2_PACKAGE_GR_OSMOSDR_HACKRF
+	bool "Osmocom HACKRF support"
+	depends on BR2_PACKAGE_HACKRF
+	help
+	  Enable Osmocom HACKRF support
+
 endif
diff --git a/package/gr-osmosdr/gr-osmosdr.mk b/package/gr-osmosdr/gr-osmosdr.mk
index b96a32a221..78c7fa30da 100644
--- a/package/gr-osmosdr/gr-osmosdr.mk
+++ b/package/gr-osmosdr/gr-osmosdr.mk
@@ -54,4 +54,11 @@ else
 GR_OSMOSDR_CONF_OPTS += -DENABLE_RFSPACE=OFF
 endif
 
+ifeq ($(BR2_PACKAGE_GR_OSMOSDR_HACKRF),y)
+GR_OSMOSDR_CONF_OPTS += -DENABLE_HACKRF=ON
+GR_OSMOSDR_DEPENDENCIES += hackrf
+else
+GR_OSMOSDR_CONF_OPTS += -DENABLE_HACKRF=OFF
+endif
+
 $(eval $(cmake-package))
-- 
2.39.2

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2023-02-23 20:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 20:18 Martin Böh via buildroot [this message]
2023-02-23 22:33 ` [Buildroot] [PATCH 1/1] package/gr-osmosdr: add support for HACKRF receivers Thomas Petazzoni via buildroot
2023-08-30 20:39 ` Thomas Petazzoni via buildroot

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=20230223201817.224238-1-contact@martb.dev \
    --to=buildroot@buildroot.org \
    --cc=contact@martb.dev \
    --cc=gwenhael.goavec-merou@trabucayre.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 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.