search

viennacl / pyviennacl-dev

Developer repository for PyViennaCL. Visit http://viennacl.sourceforge.net/ for latest releases.
MIT License
32 stars 6 forks source link

Development work-flow #14

Closed ptillet closed 10 years ago

ptillet commented 10 years ago

Hello,

I've noticed that the setup.py script triggers the compilation of all the _viennacl/*.src file whenever we modify a single one of them. Combined with the fact that multi-threaded compilation does not seem to be supported, it makes the development of a new module pretty tedious! Is there any way to alleviate this, or do I have to go on with a hard-coded script which recompiles only my module? (I'm starting to wrap the kernel generator)

tsmithe commented 10 years ago

Hm, I'll have to check, but I don't think distutils keeps track of changes like make does, annoyingly. What I ended up doing is installing ccache, which does that tracking transparently. Once it's installed, put /usr/lib/ccache on your path (I think), before /usr/bin -- at least on Debian or Ubuntu systems!

I'm looking forward to your pull request!

ptillet commented 10 years ago

Thanks for the hint :) Using 'CC="ccache gcc" python setup.py build' should be better than changing the path, though :P