Re: [Python-Dev] DRAFT: python-dev Summary for 2006-01-01 through 2006-01-15

[Ronald Oussoren]

On 26-jan-2006, at 13:29, Thomas Heller wrote:

Thomas Wouters <[EMAIL PROTECTED]> writes:

On Thu, Jan 26, 2006 at 09:54:51AM +0100, Thomas Heller wrote:

The current state is that ctypes uses GPL'd tools to build libffi, and

those can't be committed into Python SVN.

http://mail.python.org/pipermail/python-dev/2006-January/059937.html

But http://mail.python.org/pipermail/python-dev/2006-January/ 059938.html

was never responded to.

Lack of time - sorry.

And licenses are fluid, it may be a piece of cake to
get one of those 'tools' un-GPL'ed, even if they are.

I wouldn't even know whom to ask.

I just need to support two CPU architectures on one OS.

Ronald

It shouldn't be too hard to use Python's main configure script to calculate the information necessary to build libffi. A lot of it is already calculated anyway (sizeof various type, endianness), some can be hardcoded (FFI_NO_RAW_API). In PyObjC I just compile the files I need from my setup.py. But I have an easy task,

Thomas

_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev

Unsubscribe: http://mail.python.org/mailman/options/python-dev/ ronaldoussoren%40mac.com

smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com