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

Bug in NEST-INSTALLATION-SYSTEM #561

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

Comments

Projects
None yet
2 participants
@priyankarroychowdhury3

priyankarroychowdhury3 commented Nov 22, 2016

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

This comment has been minimized.

Show comment
Hide comment
@heplesser

heplesser Dec 2, 2016

Contributor

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

Contributor

heplesser commented Dec 2, 2016

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

@heplesser

This comment has been minimized.

Show comment
Hide comment
@heplesser

heplesser Apr 4, 2017

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.

Contributor

heplesser commented Apr 4, 2017

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.

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