public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Heller <theller@python.net>
To: gcc@gcc.gnu.org
Subject: libffi package
Date: Fri, 16 Jan 2004 20:17:00 -0000	[thread overview]
Message-ID: <65fbabsl.fsf@python.net> (raw)

Let me shortly introduce me:

I'm Thomas Heller, author and maintainer of the Python 'ctypes' foreign
function call package <http://starship.python.net/crew/theller/ctypes/>.

This package works on Windows, and numerous other platforms (AFAIK
GNU/Linux, cygwin, Mac OSX, BSD, Solaris).

Up to now, 'ctypes' uses libffi on all platforms except on native
Windows.  For Windows, it contains some home made functions for function
calls, and also for closures.

To reduce code duplication, I would like to replace the homemade windows
functions by calls to libffi, although libffi must be extended by some
features I need.

So here are the questions:

Are there chances that patches to libffi to compile it with the
Microsoft compiler for Windows be accepted?  Patches for windows
specific features?

Are there any ideas to provide libffi as a standalone package, separate
from GCC, again?  Would there by anything I could help to make this
happen?

What about the docs?  They haven't changed in a few years (that's my
impression at least).  Are the Linux (and other) users happy to install
libffi by grabbing it from the CVS tree?

Aren't there conflicts between various hacked snapshots of libffi
floating around?

And finally (IANAL): is the redhat license still the one which applies
to libffi?

TIA,

Thomas

             reply	other threads:[~2004-01-16 20:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-16 20:17 Thomas Heller [this message]
2004-01-20  3:50 ` Jeff Sturm
2004-01-20 20:08   ` Thomas Heller
2004-01-21  0:20     ` Tom Tromey
2004-01-22 15:07       ` Thomas Heller
2004-01-22 17:54         ` Tom Tromey
2004-01-22 19:27           ` Thomas Heller
2004-01-26 15:45             ` Tom Tromey
2004-01-27 17:26               ` Thomas Heller

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=65fbabsl.fsf@python.net \
    --to=theller@python.net \
    --cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).