From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: joakim@verona.se, emacs-devel@gnu.org
Subject: Re: FFI again
Date: Sun, 06 Oct 2013 22:04:30 +0300 [thread overview]
Message-ID: <83r4by5igx.fsf@gnu.org> (raw)
In-Reply-To: <jwv38oel119.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: joakim@verona.se, emacs-devel@gnu.org
> Date: Sun, 06 Oct 2013 14:17:30 -0400
>
> >> > I really don't like this idea. You either force users to have the Emacs
> >> > headers, Emacs import library, and a C compiler available to install a
> >> > package or you provide pre-compiled binaries for popular platforms and
> >> > create an ABI versioning nightmare.
> >> The plan would be to require headers and a C compiler.
> >> Precompiled libraries could be considered for the Windows platform, but
> >> only if we can keep the versioning nightmare in check.
> > I don't think the nightmare is as bad as it sounds. Windows users
> > already keep such nightmares in check, including with Emacs.
>
> There's some hope, indeed, but notice that the problem is a bit more
> serious than what we currently have for libgnutls and friends, because
> that precompiled code needs to link both with lib<foo> and with Emacs,
> and there's a potential version mismatch on both sides.
Just like libgnutls today, which has to link with libnettle,
linhogweed, libgmp, and p11-kit (to say nothing of the ubiquitous
libintl and zlib).
next prev parent reply other threads:[~2013-10-06 19:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 16:11 FFI again Stefan Monnier
2013-10-05 16:24 ` joakim
2013-10-05 22:18 ` Stefan Monnier
2013-10-05 22:33 ` joakim
2013-10-06 16:39 ` Stefan Monnier
2013-10-06 16:54 ` Eli Zaretskii
2013-10-06 18:17 ` Stefan Monnier
2013-10-06 19:04 ` Eli Zaretskii [this message]
2013-10-07 1:41 ` Stephen J. Turnbull
2013-10-07 3:29 ` Stefan Monnier
2013-10-07 4:34 ` Stephen J. Turnbull
2013-10-07 4:58 ` Stefan Monnier
2013-10-07 22:14 ` Andy Moreton
2013-10-07 22:47 ` Stefan Monnier
2013-10-08 6:54 ` Eli Zaretskii
2013-10-08 2:22 ` Stephen J. Turnbull
2013-10-08 2:47 ` Richard Stallman
2013-10-08 5:33 ` Stephen J. Turnbull
2013-10-08 7:14 ` Eli Zaretskii
2013-10-05 17:07 ` Eli Zaretskii
2013-10-05 23:24 ` Daniel Colascione
2013-10-06 19:19 ` Richard Stallman
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r4by5igx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
--cc=monnier@iro.umontreal.ca \
/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://git.savannah.gnu.org/cgit/emacs.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).