Ondrej Certik wrote:
> 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.

Uhm, so the real problem is that cmake fails to take the source directory
structure into account when copying build artefacts over to the build
directory?

How is that something to 'fix' in Cython?


> 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).

For testing, I build my extensions using distutils' "build_ext -i", which
creates the .so files inside the source tree (and leaves everything else
out of sight).

Stefan

_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev

Reply via email to