Currently we only install the python bindings inside a conda env, and libgalario_single.so etc. are installed outside. This works but is inconsistent. If one activates an environment, it should all be in there. Otherwise there may be two environment with different galario python bindings but they link to /usr/local/lib/libgalario_single.so and that library has the version that happened to be installed last.
Currently we only install the python bindings inside a conda env, and
libgalario_single.soetc. are installed outside. This works but is inconsistent. If one activates an environment, it should all be in there. Otherwise there may be two environment with different galario python bindings but they link to/usr/local/lib/libgalario_single.soand that library has the version that happened to be installed last.Another benefit is that this would hopefully fix building the conda-forge recipe https://travis-ci.org/conda-forge/staged-recipes/builds/281221938?utm_source=github_status&utm_medium=notification