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.

Sign up for GitHub

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

Jump to bottom

Bug in NEST-INSTALLATION-SYSTEM #561

Closed
priyankarroychowdhury3 opened this issue Nov 22, 2016 · 2 comments
Closed

Bug in NEST-INSTALLATION-SYSTEM #561

priyankarroychowdhury3 opened this issue Nov 22, 2016 · 2 comments
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: Bug Wrong statements in the code or documentation ZC: Installation DO NOT USE THIS LABEL ZP: PR Created DO NOT USE THIS LABEL

Comments

@priyankarroychowdhury3
Copy link

If absolute path is not used during cmake, message will be displayed that NEST is correctly installed but in reality when you want to call NEST by some Python file, import Python error is obtained. On further analysis, it is found that most of the necessary files in /install/lib/python2.7/site-packages are missing.

Only when absolute path is used in cmake, the installation is done accurately.
@heplesser heplesser added ZC: Installation DO NOT USE THIS LABEL I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) ZP: Pending DO NOT USE THIS LABEL S: Normal Handle this with default priority T: Bug Wrong statements in the code or documentation labels Dec 2, 2016
@heplesser
Copy link
Contributor

@jougs Could you take a look? Maybe we should ensure that CMake requires and absolute path?

@heplesser
Copy link
Contributor

As far as I understand the CMake docs, CMake should convert the relative path to an absolute one, at least in CMake 3.8. I will make explicit in our documentation that one should provide absolute paths.

@heplesser heplesser added ZP: PR Created DO NOT USE THIS LABEL and removed ZP: Pending DO NOT USE THIS LABEL labels Apr 4, 2017
@heplesser heplesser mentioned this issue Apr 4, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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: Bug Wrong statements in the code or documentation ZC: Installation DO NOT USE THIS LABEL ZP: PR Created DO NOT USE THIS LABEL
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@heplesser @priyankarroychowdhury3