Christoph Junghans
Christoph Junghans
I never found a good way to make setuptools work with cmake transparently, but if you know a solution go ahead.
To build an egg file to upload to PyPl, one basically needs a `setup.py` calling cmake, see: https://github.com/sim-x/simx/blob/master/setup.py for an example.
Here is a setuptools extension, which supports CMake: https://github.com/scikit-build/scikit-build
The other thing we could do is to mark some tests as **big**, **long** or **nightly** and have them off by default and only enable them in some of the...
How about just doing `pi_water` and `polymer_melt_tabulated` for just one time step to test the API and putting a more physical version in `examples`?
@acfogarty: then we have to decrease the system size for `pi_water`.
I am not sure how often particles really get inserted once the simulations runs.
@stuehn do we still need this?
Done for gcc in #389. ICC and clang++ sill need to be done.
@stuehn, @govarguz and I discussed that a couple of weeks ago. I think the main advantage of the fork and merge-request strategy is that, you get testing before the code...