From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Gwenhael Goavec-Merou <gwenj@trabucayre.com>
Cc: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4] package/gnuradio: bump version to 3.10.4.0
Date: Thu, 6 Oct 2022 21:50:57 +0200 [thread overview]
Message-ID: <20221006215057.49eec773@windsurf> (raw)
In-Reply-To: <1665044877-79114-1-git-send-email-gwenj@trabucayre.com>
Hello,
On Thu, 6 Oct 2022 10:27:57 +0200
Gwenhael Goavec-Merou <gwenj@trabucayre.com> wrote:
> - Since gnuradio 3.10 swig was replaced by pybind. Now python libraries,
> bindings and python wrappers are produces using pybind: this why python-pybind
> is a buildtime dependency. This one is a stagging only package (nothing
> installed into target directory -> no select BR2_PACKAGE_PYTHON_PYBIND
> added to Config.in but GNURADIO_DEPENDENCIES is updated with python-pybind).
I am sorry, but this still doesn't make any sense, and will in fact
cause build failures. A package cannot have a target package in its
<pkg>_DEPENDENCIES variable without selecting it.
If python-pybind is needed at build time on the host, then
GNURADIO_DEPENDENCIES must contain host-python-pybind, and nothing
needs to be done in Config.in.
If python-pybind is needed on the target, then two options:
(1) It's needed only at runtime => it should be selected in Config.in.
(2) It's needed at build-time => it should be selected in Config.in
*and* and added as a dependency in GNURADIO_DEPENDENCIES. However, I'd
like to see a serious justification, because it is really uncommon to
have target Python packages be build-time dependencies.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-10-06 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 8:27 [Buildroot] [PATCH v4] package/gnuradio: bump version to 3.10.4.0 Gwenhael Goavec-Merou
2022-10-06 19:50 ` Thomas Petazzoni via buildroot [this message]
2022-10-06 20:13 ` Gwenhael Goavec-Merou
2022-10-09 9:29 ` Guillaume Bres
2022-10-09 9:37 ` Guillaume Bres
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=20221006215057.49eec773@windsurf \
--to=buildroot@buildroot.org \
--cc=gwenhael.goavec-merou@trabucayre.com \
--cc=gwenj@trabucayre.com \
--cc=thomas.petazzoni@bootlin.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.