On Jun 10, 2009, at 10:41 AM, Ondrej Certik wrote: [...]
>>> Ok. So how do you propose I should fix the problem, if I need those >>> .so libraries at different place than the rest of the python source >>> files? >> >> I don't know. A hack is to have your setup.py actually move the >> __init__.py temporarily--I'm sure there's a better longterm fix >> though. Just out of curiosity, why do you need to segregate the .so >> files? > > Because we use cmake to build the project (C++ and cython) and cmake > allows to build the project out of the tree, e.g. it leaves the .cpp > and .py files in the source dir and creates a build dir, where it > stores all the .o and .so files. If the project is just C++, it is > then possible to use the build directory as is, e.g. you don't have to > install it and it still works (of course if you want, you can also > install it). > > With Cython, it doesn't work, because the .so files don't find each > other. > > One solution (besides moving __init__.py files away at each build) is > to just create an option to cython, that will disable this feature (or > pretend the __init__.py files are not there). > > I am not convinced it's worth the pain though yet. So you think one > should never need to segregate the .so file in a Python + C++ project? I don't see a reason why one should need to, but I don't claim there's never a valid reason either. More to the point, I don't see a quick or good workaround or sufficient motivation for a more complex/ disruptive one (but if you do, go ahead and look at it more). - Robert _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
