From: David Bremner <david@tethera.net>
To: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: [PATCH 3/5] build: optionally build python-cffi bindings
Date: Mon, 04 Nov 2019 20:32:34 -0400 [thread overview]
Message-ID: <87y2wvrwm5.fsf@tethera.net> (raw)
In-Reply-To: <m24kzjib9a.fsf@guru.guru-group.fi>
Tomi Ollila <tomi.ollila@iki.fi> writes:
> how bad does out-of-tree build break with this -- do we need to do
> the same as with ruby bindings (copy sources -- do we still do so)? or does
> python provide better alternative..?
Good question. What is here will break with out of tree builds, just
from trivial things like missing $(srcdir). At a deeper level someone
would probably have to modify the build bits (python-cffi/setup.py,
python-cffi/notb/_build) to work out of tree. I don't know how well any
of this is supported by the setuptools module. It seems more friendly to
the idea of building inside the source tree with destination outside,
but I'm really not a setuptools expert.
d
next prev parent reply other threads:[~2019-11-05 0:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 1:39 python CFFI bindings integration into notmuch build/test David Bremner
2019-11-04 1:39 ` [PATCH 1/5] bindings/python-cffi: preserve environment for tests David Bremner
2019-11-04 1:39 ` [PATCH 2/5] configure: check for python cffi module David Bremner
2019-11-04 21:24 ` Tomi Ollila
2019-11-04 1:39 ` [PATCH 3/5] build: optionally build python-cffi bindings David Bremner
2019-11-04 21:26 ` Tomi Ollila
2019-11-05 0:32 ` David Bremner [this message]
2020-05-22 1:06 ` Daniel Kahn Gillmor
2019-11-04 1:39 ` [PATCH 4/5] tests: run python-cffi tests David Bremner
2019-11-04 16:18 ` Tomi Ollila
2019-11-04 16:57 ` David Bremner
2019-11-04 21:45 ` Tomi Ollila
2019-11-04 22:04 ` Tomi Ollila
2019-11-06 2:19 ` David Bremner
2019-11-06 20:51 ` Tomi Ollila
2019-11-09 1:36 ` David Bremner
2019-11-09 21:59 ` Tomi Ollila
2019-11-22 3:03 ` David Bremner
2019-11-26 0:52 ` David Bremner
2019-12-03 12:16 ` David Bremner
2019-11-04 1:39 ` [PATCH 5/5] travis: add python3-{cffi,pytest,setuptools} David Bremner
2019-11-04 11:10 ` python CFFI bindings integration into notmuch build/test David Bremner
2019-11-05 20:47 ` Tomi Ollila
2019-11-06 2:22 ` David Bremner
2019-11-14 18:52 ` Floris Bruynooghe
2019-11-14 20:20 ` Tomi Ollila
2019-11-14 22:24 ` Floris Bruynooghe
2019-11-14 23:09 ` Floris Bruynooghe
2019-11-16 15:51 ` David Bremner
2019-11-17 14:40 ` Floris Bruynooghe
2019-11-17 16:09 ` David Bremner
2019-11-16 15:43 ` David Bremner
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2wvrwm5.fsf@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).