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 v2] package/gnuradio: bump version to 3.10.3.0
Date: Fri, 23 Sep 2022 11:01:59 +0200 [thread overview]
Message-ID: <20220923110159.558e373f@windsurf> (raw)
In-Reply-To: <20220923104005.30fed5a3@x230_1.trabucayre.com>
Hello,
On Fri, 23 Sep 2022 10:40:05 +0200
Gwenhael Goavec-Merou <gwenj@trabucayre.com> wrote:
> > > + select BR2_PACKAGE_PYTHON_NUMPY
> >
> > Why are you removing the "# runtime" comment here? Your patch doesn't
> > change numpy to a build time dependency.
> >
> Your review of v1 has highliteted the fact numpy is required at runtime (of
> course) but also at the buildtime (cmake checks for dependencies and stop when
> a requirement isn't satisfied). This why I have removed this comment.
But how come target numpy is needed at *build* time ? Isn't this just a
silly check that makes sense in native build situation, but not in
cross-compilation situation ?
> > > ifeq ($(BR2_PACKAGE_GNURADIO_PYTHON),y)
> > > -GNURADIO_DEPENDENCIES += python3
> > > +GNURADIO_DEPENDENCIES += python3 python-pybind \
> > > + host-python-numpy host-python-packaging
> >
> > Could you clarify if you need python-pybind on the target or on the
> > host? And also explain in the commit log why host-python-numpy and
> > host-python-packaging are now needed?
> True. I will do that. And bump to the 3.10.4.0 version at the same time.
Thanks! Make sure to be very clear on the explanations of which
dependency is needed on the host vs. on the target, and which is needed
at build time vs. run time.
Thanks a lot!
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-09-23 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 13:04 [Buildroot] [PATCH v2] package/gnuradio: bump version to 3.10.3.0 Gwenhael Goavec-Merou
2022-09-17 15:57 ` Thomas Petazzoni
2022-09-23 8:40 ` Gwenhael Goavec-Merou
2022-09-23 9:01 ` Thomas Petazzoni via buildroot [this message]
2022-09-23 12:42 ` Gwenhael Goavec-Merou
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=20220923110159.558e373f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox