Oh, (sorry for the triple post everyone) omitting it will also make it that you do not need to source any nest vars anymore either. activate the python env, and the nest that you installed for that env will be active as well
On top of that, please do not specify any DCMAKE_INSTALL_PREFIX. Using that toggles on an "expert user" build. If you omit it, nest will ne automatically installed inside of your current Python env, and the chances of successful detection are considerably higher
On Fri, Oct 18, 2024, 19:22 Robin De Schepper <robin.deschepper93@gmail.com> wrote:Try again WITHOUT specifying any paths yourself: If your venv is active, they should be the first ones to be detected. could you compare the versions of cython in the build log with that given by pip show cython?
On Fri, Oct 18, 2024, 19:20 Ady Sharma <aadhar.sharma@bcf.uni-freiburg.de> wrote:Hello Robin,
Thanks for you reply!
I'm already using a Python virtual environment with the paths to CMake and Cython correctly specified. I retried your suggestion just in case, but, sadly, it produces the same issue.
Could you suggest what else might be going wrong here? Thanks!
Best,
Ady
_______________________________________________
NEST Users mailing list -- users@nest-simulator.org
To unsubscribe send an email to users-leave@nest-simulator.org