unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Carl Worth <cworth@cworth.org>
To: Adrian Perez de Castro <aperez@igalia.com>, notmuch@notmuchmail.org
Subject: Re: SWIG (and particularly Python) bindings
Date: Wed, 20 Jan 2010 21:48:57 +1300	[thread overview]
Message-ID: <87iqax5fgm.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <20091230115223.1b3472a1@hikari>

[-- Attachment #1: Type: text/plain, Size: 981 bytes --]

On Wed, 30 Dec 2009 11:52:23 +0100, Adrian Perez de Castro <aperez@igalia.com> wrote:
> BTW, I think that if more bindings start to appear, Notmuch might be built
> as a shared library, to avoid duplicating it everywhere.

Yes. As soon as we have users of the library we can install it as a
shared library.

>                                                          One option may be
> using *just* libtool but not the rest of auto-foo tools (for the record:
> I agree with Carl that they are slow and wicked).

Totally uninterested in libtool personally. It does so many things wrong
(.la files that *only* cause breakage on Linux, a tendency to shove
hard-coded rpath entries in the library where unwanted), and doesn't
seem to do much of anything that's really interesting. I'm happy to just
accept patches that tweak the command in the Makefile for "build a
shared library now" for each platform that's of practical interest. The
job here is just not that complicated.

-Carl

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2010-01-20  8:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-29  9:16 SWIG (and particularly Python) bindings Ben Gamari
2009-12-30 10:52 ` Adrian Perez de Castro
2009-12-30 11:34   ` Scott Robinson
2010-01-16  4:09     ` Ben Gamari
2010-01-16  4:28       ` [PATCH] libtoolize notmuch Ben Gamari
2010-01-20  8:51         ` Carl Worth
2009-12-30 16:10   ` SWIG (and particularly Python) bindings Ben Gamari
2010-01-20  8:48   ` Carl Worth [this message]
2010-01-20  8:45 ` Carl Worth
2010-01-20 18:39   ` Ben Gamari

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=87iqax5fgm.fsf@yoom.home.cworth.org \
    --to=cworth@cworth.org \
    --cc=aperez@igalia.com \
    --cc=notmuch@notmuchmail.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.
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).