From: unspecd <unspecd@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] gnuradio: update to 3.10.0.0.
Date: Mon, 17 Jan 2022 14:10:20 +0100 [thread overview]
Message-ID: <20220117131020.GaHU5kAgsLRmfA6MnRzctFU5TPbMPAUZ4b4a3YvO9Y0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35049@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
New review comment by unspecd on void-packages repository
https://github.com/void-linux/void-packages/pull/35049#discussion_r785992198
Comment:
This is used internally to generate Python bindings. In the release tarballs these binding are pre-generated. In any case, it would be nice to have this package in Void.
Here is what the [documentation](https://github.com/gnuradio/gnuradio/blob/master/docs/PYBIND11.md) says:
---
### Generating/maintaining Python bindings using Pybind11
As of the GNU Radio 3.9 release, python bindings are handled using pybind11, which is inherently different than they were in previous releases
#### Dependencies
- pybind11 > 2.4.3 https://pybind11.readthedocs.io/
- pygccxml https://pygccxml.readthedocs.io/en/develop/install.html
- This is an optional dependency and basic functionality for OOT generation can be performed without pygccxml
- It is required for automatically generating bindings for most of the GR source tree
...
Each block binding file contains an automatically generated and maintained comment block that informs CMake when the bindings are out of sync with the header file they refer to, and what to do about it
next prev parent reply other threads:[~2022-01-17 13:10 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 16:25 [PR PATCH] gnuradio: update to 3.9.5.0 unspecd
2022-01-14 20:34 ` unspecd
2022-01-14 20:36 ` unspecd
2022-01-15 5:04 ` [PR PATCH] [Updated] " unspecd
2022-01-15 6:34 ` [PR PATCH] [Updated] gnuradio: update to 3.10.0.0 unspecd
2022-01-15 6:38 ` unspecd
2022-01-15 6:45 ` unspecd
2022-01-15 6:55 ` [PR PATCH] [Updated] " unspecd
2022-01-15 20:12 ` unspecd
2022-01-15 22:08 ` unspecd
2022-01-17 9:03 ` [PR REVIEW] " ericonr
2022-01-17 9:03 ` ericonr
2022-01-17 9:03 ` ericonr
2022-01-17 11:10 ` unspecd
2022-01-17 11:10 ` unspecd
2022-01-17 13:10 ` unspecd [this message]
2022-01-18 10:35 ` [PR PATCH] [Updated] " unspecd
2022-01-18 10:35 ` unspecd
2022-01-18 10:40 ` unspecd
2022-01-18 11:04 ` [PR PATCH] [Updated] " unspecd
2022-01-18 11:06 ` unspecd
2022-01-21 7:33 ` [PR PATCH] [Updated] " unspecd
2022-01-22 5:54 ` unspecd
2022-01-29 4:25 ` unspecd
2022-01-29 9:37 ` unspecd
2022-01-29 9:39 ` unspecd
2022-01-29 10:50 ` unspecd
2022-02-01 8:38 ` [PR PATCH] [Updated] " unspecd
2022-02-02 9:11 ` unspecd
2022-02-02 10:21 ` gnuradio: update to 3.10.1.0 unspecd
2022-02-02 10:27 ` [PR PATCH] [Updated] " unspecd
2022-02-02 11:10 ` unspecd
2022-02-02 11:12 ` unspecd
2022-02-04 11:24 ` [PR PATCH] [Updated] gnuradio: update to 3.10.1.1 unspecd
2022-02-20 8:34 ` unspecd
2022-03-31 8:09 ` unspecd
2022-03-31 8:10 ` unspecd
2022-04-11 16:29 ` [PR PATCH] [Updated] " unspecd
2022-04-14 7:59 ` unspecd
2022-04-14 12:52 ` unspecd
2022-04-18 1:00 ` [PR PATCH] [Updated] " unspecd
2022-06-21 22:24 ` [PR PATCH] [Updated] gnuradio: update to 3.10.2.0 unspecd
2022-06-21 22:27 ` gnuradio: update to 3.10.3.0 unspecd
2022-06-22 18:37 ` classabbyamp
2022-06-27 3:37 ` unspecd
2022-06-28 3:23 ` classabbyamp
2022-06-28 5:23 ` [PR PATCH] [Updated] " unspecd
2022-06-28 14:53 ` unspecd
2022-06-28 15:36 ` unspecd
2022-06-28 15:36 ` unspecd
2022-07-17 16:27 ` Noah-Huppert
2022-07-17 18:56 ` ericonr
2022-07-17 18:57 ` ericonr
2022-07-17 21:59 ` [PR PATCH] [Updated] " unspecd
2022-07-17 22:44 ` unspecd
2022-07-19 15:47 ` [PR REVIEW] " sgn
2022-07-19 17:06 ` [PR PATCH] [Updated] " unspecd
2022-07-19 17:10 ` [PR REVIEW] " unspecd
2022-07-19 17:10 ` unspecd
2022-07-27 6:30 ` sgn
2022-07-27 11:02 ` [PR PATCH] [Updated] " unspecd
2022-07-27 11:05 ` unspecd
2022-07-27 13:15 ` unspecd
2022-07-28 7:17 ` [PR PATCH] [Updated] " classabbyamp
2022-07-28 7:18 ` [PR PATCH] [Merged]: " classabbyamp
2022-07-28 7:19 ` classabbyamp
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=20220117131020.GaHU5kAgsLRmfA6MnRzctFU5TPbMPAUZ4b4a3YvO9Y0@z \
--to=unspecd@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).