Skip to content

Comments

Add venv option for source installation in docs#3710

Open
jessica-mitchell wants to merge 2 commits intonest:masterfrom
jessica-mitchell:install-venv-source
Open

Add venv option for source installation in docs#3710
jessica-mitchell wants to merge 2 commits intonest:masterfrom
jessica-mitchell:install-venv-source

Conversation

@jessica-mitchell
Copy link
Contributor

This adds another option besides no environment and mamba for using source install
@terhorstd need to check dependencies, as nestbuildmatrix and noenv were quite different.
Assumes readline and libncurses is not needed (expecting pynest-ng)

@jessica-mitchell jessica-mitchell added the S: Normal Handle this with default priority label Dec 16, 2025
@jessica-mitchell jessica-mitchell added T: Maintenance Work to keep up the quality of the code and documentation. I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) labels Dec 16, 2025
@github-project-automation github-project-automation bot moved this to In progress in Documentation Dec 16, 2025
Comment on lines +78 to +84
For your convenience, a shell script setting all required environment variables is provided in
``<nest_install_dir>/bin/nest_vars.sh``. Setting the environment variables in your active shell session requires
sourcing the script:

.. code-block:: bash

source <nest_install_dir>/bin/nest_vars.sh
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The nest_vars.sh is not necessary when installing into an environment (venv, conda, mamba, etc.), as long as CMAKE_INSTALL_PREFIX was not specified in the cmake command. The activation of the envrionment source venv/bin/activate is exactly what source …/bin/nest_vars.sh does when NEST is installed outside an environment.

Co-authored-by: Dennis Terhorst <terhorstd@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Maintenance Work to keep up the quality of the code and documentation.

Projects

Status: In progress

Development

Successfully merging this pull request may close these issues.

2 participants