Malek Hadj-Ali wrote:
Hi,Pyev (http://code.google.com/p/pyev/) is a python extension wrapper around libev.
As I had issues compiling/installing it ... I took some countermeasures.As I doubt its usefull to ship the binding with libev itself, I decided to make it use a local libev installation. The code to detect python 3.1 did not work with python 3.1a+ as the version numbers are strings instead of ints.
I wrapped the setup.py thing into an automake container, which creates setup.py from setup.py.in, filling the pathes for libev library and header, including python version detection.
The LIBEV_VERSION you grabbed from libevs configure.ac is the only problem, as I can't get that information.
I'd really appreciate if you could apply these changes to pyev, as they make it work.
to use: autoreconf -vi ./configure --help make install make dist for me:autoreconf -vi; ./configure --with-ev-include=/opt/libev/include --with-ev-lib=/opt/libev/lib/ --with-python=/usr/bin/python3.1; make install; make dist
-Wl,rpath is set, so the library is linked correctly. A real great feature:if you embed python into your libev powered application, you can use these bindings to insert watchers into your applications ev_default_loop from python, great work!
As a diff is larger than the whole thing packed, there is a tar attached. Markus
pyev_automake.tar.bz2
Description: application/bzip
_______________________________________________ libev mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
