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

Added --nest-top-dir flag to allow nestpy to be set to use user's NEST source code instead of that in src/nestpy/ #29

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jpbrodsky
Copy link

usage: python setpy.py install --nest-top-dir="/path/to/NEST/"
(pip install nestpy --install-option="/path/to/NEST/" might work?)

Nest top dir should include src/ and include/ directories, as with the NEST git repo

…T source code instead of that in src/nestpy/

usage: python setpy.py install --nest-top-dir="/path/to/NEST/"

Nest top dir should include src/ and include/ directories, as with the NEST git repo
@tunnell
Copy link
Member

tunnell commented Mar 15, 2020

Right now, nest is building against it's own copy of the code that puts it in one folder. The whole C++ nest is shipped to aid installation. However, if you're modifying your own NEST, I agree this is useful! Will merge for next release.

Next release would be with the next NEST release, but can make an intermediate nestpy release if necessary.

@tunnell
Copy link
Member

tunnell commented Jun 22, 2020

@jpbrodsky can you update your branch with the main branch to see if the tests pass with custom version?

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

Successfully merging this pull request may close these issues.

2 participants