unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: johnw@newartisans.com, naesten@gmail.com,
	monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: FFI in Emacs
Date: Wed, 11 Jul 2012 21:30:36 +0300	[thread overview]
Message-ID: <83liiqb16b.fsf@gnu.org> (raw)
In-Reply-To: <87y5mq40nh.fsf@uwakimon.sk.tsukuba.ac.jp>

> From: "Stephen J. Turnbull" <stephen@xemacs.org>
> Cc: Samuel Bronson <naesten@gmail.com>,
>     johnw@newartisans.com,
>     monnier@iro.umontreal.ca,
>     emacs-devel@gnu.org
> Date: Thu, 12 Jul 2012 03:23:46 +0900
> 
> Eli Zaretskii writes:
> 
>  > > >> [SXEmacs FFI interface] should be fairly easily portable to Emacs on
>  > > >> platforms that have libffi.  It probably doesn't work on Windows
>  > > >
>  > > > Why not?  Not because of libffi, I think.
> 
> Because there is no support for Windows in SXEmacs at all, and last I
> looked XEmacsen do not use the same technology for loading DLLs on
> Windows that they do on Unix, so there is no provision whatsoever in
> the SXEmacs code for actually loading the C code that the Lisp FFI API
> allows you to call.

Well, if they don't use libltdl or something similar for loading
(which is a natural choice when using libffi, but YMMV), then I guess
you are right, it might not work.

> Come to think of it, I am assuming a "native" build with VC; maybe it
> would work with the "Unix" code on Cygwin/Mingwin.

MinGW uses the same APIs as VC, so I doubt that.  Cygwin is another
matter, of course.



  reply	other threads:[~2012-07-11 18:30 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27 23:36 FFI in Emacs Aurélien Aptel
2012-06-27 23:47 ` Glenn Morris
2012-06-28  0:03   ` John Wiegley
2012-06-28  2:12     ` Glenn Morris
2012-06-28  3:43       ` Stefan Monnier
2012-06-28  4:51         ` John Wiegley
2012-06-28 15:27           ` Nix
2012-07-11  5:24         ` John Wiegley
2012-07-11  5:53           ` Helmut Eller
2012-07-11  6:43           ` Michael Albinus
2012-07-11 14:04             ` Burton Samograd
2012-07-11 14:07               ` Burton Samograd
2012-07-11  7:14           ` Stephen J. Turnbull
2012-07-11  7:44             ` Michael Albinus
2012-07-11 16:11             ` Eli Zaretskii
2012-07-11 17:08               ` Samuel Bronson
2012-07-11 17:49                 ` Eli Zaretskii
2012-07-11 18:23                   ` Stephen J. Turnbull
2012-07-11 18:30                     ` Eli Zaretskii [this message]
2012-07-11 16:05           ` Eli Zaretskii
2012-07-12 13:55           ` Stefan Monnier
2012-07-12 17:01             ` Samuel Bronson
2012-07-12 18:54             ` John Wiegley
2012-07-12 23:19             ` Sam Steingold
2012-07-13  2:20               ` Óscar Fuentes
2012-07-13  3:21                 ` Stephen J. Turnbull
2012-06-28  6:20       ` joakim
2012-07-11  9:40         ` joakim
2012-08-25 17:25           ` Aurélien Aptel
2012-08-25 18:20             ` joakim
2012-08-26  8:57               ` Ivan Kanis
2012-08-26 13:11                 ` joakim
2013-03-12 19:16             ` Aurélien Aptel
2013-03-12 21:50               ` Eli Zaretskii
2013-03-12 22:40                 ` Pascal J. Bourguignon
2013-03-13  7:41                   ` Andreas Schwab
2013-03-12 22:53                 ` Aurélien Aptel
2013-03-13  0:31                   ` Daniel Colascione
2013-03-13  3:55                   ` Eli Zaretskii
2013-03-22 19:44               ` BT Templeton
2013-03-23  1:51                 ` Leo Liu
2013-03-23  2:04                   ` Noah Lavine
2013-03-23 16:07                 ` Stefan Monnier
2013-03-23 18:33                   ` Yagnesh Raghava Yakkala

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=83liiqb16b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=johnw@newartisans.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=naesten@gmail.com \
    --cc=stephen@xemacs.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://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).