Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gwenhael Goavec-Merou <gwenj@trabucayre.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 4/5] package/gnuradio: add gr-network block support
Date: Wed, 22 Feb 2023 17:26:42 +0100	[thread overview]
Message-ID: <20230222172621.4994893c@x230> (raw)
In-Reply-To: <20230222160514.2069544-4-fontaine.fabrice@gmail.com>

On Wed, 22 Feb 2023 17:05:13 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> grnet networking block support is available since version version
> 3.9.0.0 and
> https://github.com/gnuradio/gnuradio/commit/cc37c3e8cd5eabcb5c9d919e5fffc5d938690140
> 
> gr-network is a mandatory dependency of latest gqrx
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  package/gnuradio/Config.in   | 6 ++++++
>  package/gnuradio/gnuradio.mk | 6 ++++++
>  2 files changed, 12 insertions(+)
> 
> diff --git a/package/gnuradio/Config.in b/package/gnuradio/Config.in
> index 1824589263..51237e62b9 100644
> --- a/package/gnuradio/Config.in
> +++ b/package/gnuradio/Config.in
> @@ -134,6 +134,12 @@ config BR2_PACKAGE_GNURADIO_FILTER
>  	help
>  	  Filter signal processing blocks
>  
> +config BR2_PACKAGE_GNURADIO_NETWORK
> +	bool "gr-network support"
> +	select BR2_PACKAGE_GNURADIO_BLOCKS
> +	help
> +	  TCP and UDP source/sink blocks
> +
>  config BR2_PACKAGE_GNURADIO_QTGUI
>  	bool "gr-qtgui"
>  	depends on BR2_PACKAGE_GNURADIO_PYTHON
> diff --git a/package/gnuradio/gnuradio.mk b/package/gnuradio/gnuradio.mk
> index 59fb23d89d..d9218b533d 100644
> --- a/package/gnuradio/gnuradio.mk
> +++ b/package/gnuradio/gnuradio.mk
> @@ -106,6 +106,12 @@ else
>  GNURADIO_CONF_OPTS += -DENABLE_GR_FILTER=OFF
>  endif
>  
> +ifeq ($(BR2_PACKAGE_GNURADIO_NETWORK),y)
> +GNURADIO_CONF_OPTS += -DENABLE_GR_NETWORK=ON
> +else
> +GNURADIO_CONF_OPTS += -DENABLE_GR_NETWORK=OFF
> +endif
> +
>  ifeq ($(BR2_PACKAGE_GNURADIO_PYTHON),y)
>  GNURADIO_DEPENDENCIES += python3 python-pybind \
>  	host-python-numpy host-python-packaging
> -- 
> 2.39.0
> 
Acked-by: Gwenhael Goavec-merou <gwenhael.goavec-merou@trabucayre.com>

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

  reply	other threads:[~2023-02-22 16:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 16:05 [Buildroot] [PATCH 1/5] package/gnuradio: drop unrecognized volk variables Fabrice Fontaine
2023-02-22 16:05 ` [Buildroot] [PATCH 2/5] package/gnuradio: disable examples Fabrice Fontaine
2023-02-22 16:19   ` Gwenhael Goavec-Merou
2023-02-22 16:05 ` [Buildroot] [PATCH 3/5] package/gnuradio: add libsndfile optional dependency Fabrice Fontaine
2023-02-22 16:31   ` Gwenhael Goavec-Merou
2023-02-22 16:05 ` [Buildroot] [PATCH 4/5] package/gnuradio: add gr-network block support Fabrice Fontaine
2023-02-22 16:26   ` Gwenhael Goavec-Merou [this message]
2023-02-22 16:05 ` [Buildroot] [PATCH 5/5] package/gqrx: bump to version 2.15.9 Fabrice Fontaine
2023-02-22 16:14 ` [Buildroot] [PATCH 1/5] package/gnuradio: drop unrecognized volk variables Gwenhael Goavec-Merou
2023-02-22 20:58 ` 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=20230222172621.4994893c@x230 \
    --to=gwenj@trabucayre.com \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@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