Gerhard Häring wrote:
#!/bin/sh
python setup.py build
cp build/lib.*/*.so .
python test.py
"python setup.py build_ext -i" is your friend. It installs the
extensions inplace. No need for cp here. :)
Christian
--
http://mail.python.org/mailman/listinfo/python-list
Martin v. Löwis wrote:
I've tried using automake, however I'm worried about libtool not getting
the options right while building my module.
You should use python-config(1) to obtain the command line options
necessary to build and link extension modules.
HTH,
Martin
Sweet, I think th
Gerhard Häring wrote:
Michael George wrote:
I've tried using automake,
In my opinion, this is serious overkill. automake is good for making
stuff work on a herd of different Unixen with various combinations of
libc functions available etc. But for developing a Python extension,
it doesn't h
> I've tried using automake, however I'm worried about libtool not getting
> the options right while building my module.
You should use python-config(1) to obtain the command line options
necessary to build and link extension modules.
HTH,
Martin
--
http://mail.python.org/mailman/listinfo/python
Michael George wrote:
Hello,
(Please CC me in replies, as I am off-list)
Ok, but please reply publicly.
I'm building an application (a game) in python, with a single C module
containing some performance-critical code. I'm trying to figure out the
best way to set it up to build.
Use dist
Hello,
(Please CC me in replies, as I am off-list)
I'm building an application (a game) in python, with a single C module
containing some performance-critical code. I'm trying to figure out the
best way to set it up to build. Distutils seems to be designed only for
building and distributing
