Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add non-default install path option to NESTCodeGeneratorUtils.generate_code_for() #972

Closed
clinssen opened this issue Oct 16, 2023 · 3 comments · Fixed by #975
Closed

Add non-default install path option to NESTCodeGeneratorUtils.generate_code_for() #972

clinssen opened this issue Oct 16, 2023 · 3 comments · Fixed by #975

Comments

@clinssen
Copy link
Contributor

On the EBRAINS image, NESTML tries to copy the generated .so user extension module into the NEST Simulator install directory, which is not writeable by the user.

Add a feature to install this to another location, or use mkstemp to automatically find a suitable location.

@pnbabu
Copy link
Contributor

pnbabu commented Oct 16, 2023

We have the option to install the binaries to another location via the install_path argument to the generate_target() function. This is used in this notebook which runs fine with the recent EBRAINS-23.09-rc2 image for EBRAINS.

@clinssen
Copy link
Contributor Author

Yes, but all tutorial notebooks currently use NESTCodeGeneratorUtils.generate_code_for(). We indeed just have to pass the parameter in the right way—or have generate_code_for() generate a temporary directory (using mkstemp) if the supplied install_path equals None.

@terhorstd
Copy link
Contributor

I've added the install_path to the notebook, so that it passes the tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants