build: added Windows OS support and compatibility #69
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Added Windows-specific installation instructions - Fix path separators to use OS-dependent ones - Updated dependency packages for simulation examples
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Why these path changes for Windows
In Windows, paths have inverse slashes (C:\Users\my_user\Documents) whereas in Linux they are the other way (/home/my_user/Documents/). To make sure the scripts are compatible with both cases, and that they are platform-independent,
os.path('..')adapts it to the current OS format.Why WSL usage
WSL has to be installed because nest-simulator is not supported in Windows (see nest documentation).
The files that don't need nest-simulator can be run in Windows. That's another reason why the paths have to be consistent in different OS.