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

Python libraries not installed in appropriate python directories #12

Closed
sanjayankur31 opened this Issue Oct 22, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@sanjayankur31
Copy link
Contributor

sanjayankur31 commented Oct 22, 2018

This was also picked up during the Fedora package review. I wasn't sure, but I looked at the examples in NEST, which say that the libneurosim python bits should be available in PYTHONPATH. So, I expect that the libpyneurosim shared objects should go to /usr/{lib,64}/pythonX.Y/site-packages/?

I'm looking at the docs to see if there's a way of setting the right installation directories for these in Autotools. (In the RPM, I can manually move the files to the correct location.)

sanjayankur31 added a commit to sanjayankur31/libneurosim that referenced this issue Oct 25, 2018

sanjayankur31 added a commit to sanjayankur31/libneurosim that referenced this issue Oct 25, 2018

@mdjurfeldt

This comment has been minimized.

Copy link
Collaborator

mdjurfeldt commented Nov 23, 2018

Hi Sanjay,

libpyneurosim is not a Python extension. It is rather support for using connection generators written in Python from C++ code (i.e. the reverse of what Python extensions do). Therefore, libpyneurosim should be installed in ordinary library directories like /usr/lib{,64}. NEST needs to link against both libpyneurosim and libneurosim and these libraries need to be found at link time by the NEST binary.

Also, this means that the comment in the NEST example is wrong. These libraries should not be on PYTHONPATH but on LD_LIBRARY_PATH (if needed).

I've commited an explanation in the libneurosim README.md.

@sanjayankur31

This comment has been minimized.

Copy link
Contributor

sanjayankur31 commented Nov 24, 2018

Ah, that clarifies it. Thanks very much @mdjurfeldt . I've closed the PR, and I'll open one against NEST to correct the comment there. Closing this ticket too.

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