Skip to content

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
jpbrodsky wants to merge 1 commit into
NESTCollaboration:masterfrom
jpbrodsky:customNEST
Open

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
jpbrodsky wants to merge 1 commit into
NESTCollaboration:masterfrom
jpbrodsky:customNEST

Conversation

@jpbrodsky

Copy link
Copy Markdown

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

tunnell commented Mar 15, 2020

Copy link
Copy Markdown
Member

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

tunnell commented Jun 22, 2020

Copy link
Copy Markdown
Member

@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