-
Notifications
You must be signed in to change notification settings - Fork 11
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
Preparing the FLI SDK Dependency #1
Comments
Here is what I needed to do on Ubuntu 12.04 to get my camera working. dowload FLI SDK >= 1.104 and FLI Linux Kernel Module >= 1.3 from fliusb install user@...:~$ cd ../fliusb-1.3 As root, (or use sudo) run: root@...$ mkdir /lib/modules/ to check install, should show something similar to: FLI USB device found: 'Camera Name' then you loaded your driver successfully. If you would like to load driver during each computer boot, add fliusb to /etc/modules. libfli install Then as normal user: make sure updated makefile is copied to the libfli-1.104 folder camera permissions modify udev rules, add a file contents of file should be: Finger Lakes CameraKERNEL=="fliusb*", MODE="666", GROUP="plugdev" Make sure that the GROUP is one that the desired user is a part of (check by typing reload with and unplug/replug camera double check correct permissions with install python-FLI Then, a quick check of the camera in python
|
If you are getting an error message like
OSError: libfli.so: cannot open shared object file: No such file or directory
it is very likely that the FLI SDK hasn't been compiled and installed properly.
There are a few steps that one needs to prepare FLI's SDK so that python-FLI can provide access to the C library.
First, the SDK must be compiled as a shared object/dynamic library (.so file) rather than the default, which is a static object (.a file). I have just posted a replacement Makefile that can be dropped in the libfli-1.104 source package folder. Then one can run
make clean
(if code was already compiled) thenmake install
(as root). That should build the library so that it can be handled by the Python ctypes module (python-FLI is just a slightly more convenient OO wrapper for this foreign function interface module) and copy it to/usr/local/lib
.Now depending on the target Linux system
/usr/local/lib
might not be on the dynamic libraries path. There are many ways to get this library found, but I have a few suggestions in order of least hacky first. On Ubuntu and similar, that path could be added to the end of file/etc/ld.so.conf
, which is updated next by runningldconfig
. If that doesn't seem to work, you could create a symbolic link like this:sudo ln -s /usr/local/lib/libfli.so /usr/lib
If ctypes is still having trouble finding the library, you could always just drop it into the python package folder (probably somewhere like
/usr/local/lib/python2.7/dist-packages/FLI-dev-py2.7.egg/FLI/
)The text was updated successfully, but these errors were encountered: