From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New packages: python3-breathe and python3-pybind11
Date: Fri, 01 May 2020 03:44:33 +0200 [thread overview]
Message-ID: <20200501014433.OIstr8OYayoXiYj1T0LTtd-6FiW_BkwPi7TZqkHnXFA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20218@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 759 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/20218#issuecomment-622208538
Comment:
pybind11 upstream is still debating the right way to support CMake modules compatible with cross-compilation environments as in Void. However, the CMake modules are not used by the pybind11 headers; they are offered to support tests and as a convenience to dependent projects. I've opted not to install the CMake modules to avoid potential breakage for any new projects that might want to leverage pybind11. If upstream figures out a suitable method, we can add the CMake modules in a later release.
In the meantime, the `python3-pybind11` module remains useful without the CMake modules and should be ready to go.
next prev parent reply other threads:[~2020-05-01 1:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20218@inbox.vuxu.org>
2020-03-19 18:25 ` Chocimier
2020-03-19 18:28 ` Chocimier
2020-03-19 18:56 ` ahesford
2020-03-19 19:01 ` ahesford
2020-03-20 19:56 ` Chocimier
2020-03-23 14:07 ` ahesford
2020-03-23 15:06 ` ahesford
2020-05-01 1:39 ` [PR PATCH] [Updated] " ahesford
2020-05-01 1:44 ` ahesford [this message]
2020-05-18 15:22 ` ahesford
2020-05-18 15:24 ` ahesford
2020-05-18 15:27 ` ahesford
2020-05-18 17:42 ` [PR PATCH] [Merged]: " abenson
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=20200501014433.OIstr8OYayoXiYj1T0LTtd-6FiW_BkwPi7TZqkHnXFA@z \
--to=ahesford@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).