From: gspe <gspe@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Pybind11
Date: Tue, 10 Mar 2020 15:32:07 +0100 [thread overview]
Message-ID: <20200310143207.Hrgo58IFHYqmppB7rYE0F-oiqVoK9YfYli20Q_Slhwg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18873@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
New comment by gspe on void-packages repository
https://github.com/void-linux/void-packages/pull/18873#issuecomment-597118155
Comment:
This template doesn't build python files and has unnecessary dependency `depends="boost python3" `
The follow template works, and should cross-compile:
```
# Template file for 'pybind11'
pkgname=pybind11
version=2.4.3
revision=1
build_style=cmake
configure_args="-D PYTHON_INCLUDE_DIR=ON -D PYBIND11_MASTER_PROJECT=ON -D PYBIND11_TEST=OFF"
hostmakedepends="python3-devel python3-setuptools"
makedepends="python3-devel"
short_desc="Seamless operability between C++11 and Python"
maintainer="Giuseppe Fierro <gspe@ae-design.ws>"
license="BSD-3-Clause"
homepage="https://pybind11.readthedocs.io"
distfiles="https://github.com/pybind/${pkgname}/archive/v${version}.tar.gz"
checksum=1eed57bc6863190e35637290f97a20c81cfe4d9090ac0a24f3bbf08f265eb71d
# build python package
post_build() {
# cmake already install pybind11 headers
export PYBIND11_USE_CMAKE=ON
python3 setup.py build
python3 setup.py install --prefix=/usr --root=${DESTDIR}
}
post_install() {
vlicense LICENSE
}
```
next prev parent reply other threads:[~2020-03-10 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18873@inbox.vuxu.org>
2020-02-11 11:39 ` Pybind11 voidlinux-github
2020-02-11 11:39 ` Pybind11 voidlinux-github
2020-03-05 20:22 ` Pybind11 yopito
2020-03-10 14:32 ` gspe [this message]
2020-05-18 17:59 ` Pybind11 ahesford
2020-05-20 20:23 ` [PR PATCH] [Closed]: Pybind11 Chocimier
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=20200310143207.Hrgo58IFHYqmppB7rYE0F-oiqVoK9YfYli20Q_Slhwg@z \
--to=gspe@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).