Davide Andreoli ha scritto il 15/11/2015 alle 12:14:
> First: I highly suggest to always build from tarballs, to not have to
> bother with cython at all.
I understand this, but my script do update git and build all I need, so
I would prefer to not make it also download every time a new tarball
fr
2015-11-15 11:25 GMT+01:00 Massimo Maiurana :
> I'm not trying to build from a tarball but from git sources, so I don't
> have any pre-generated C files.
> But I remember there was a way to tell it to use a different Cython, and
> remember that for some time I've had a compiled Cython source just
I'm not trying to build from a tarball but from git sources, so I don't
have any pre-generated C files.
But I remember there was a way to tell it to use a different Cython, and
remember that for some time I've had a compiled Cython source just to
build python-efl. That's until I didn't need it anym
With the tarballs you have the option of using either the
pre-generated C files or generating them with Cython.
It should use the pre-generated sources by default and I have no idea
why it's not doing this on your system, but you can force it with
env DISABLE_CYTHON=1 python setup.py build
These
I can't build python-efl on debian testing because it ships cython
0.23.2, but I remember there was a way to build it with a locally
installed cython via a command line option, and if I'm not wrong you
told me about this way. Can you please enlighten me once again? :)
Ciao e grazie
Massimo
Davide
