-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Fluiddpi missing input_raspicam.so #28
Comments
FWIW, I tracked down to this line: https://github.com/jacksonliam/mjpg-streamer/blob/master/mjpg-streamer-experimental/plugins/input_raspicam/CMakeLists.txt#L2, and understood what @ilektron was saying. |
As a workaround I was able to just change the CMakeLists.txt for the input_raspicam to look in /usr/include/interface for the required library headers and then update all the /opt/vc filepaths to /usr/include/interface. After the change and recompiling, make install, everything things to be working. I think in the latest releases of pi base images the pi specific headers were moved from /opt/vc into /usr/include |
It appears that in this issue, the developer of To do that in fluidd, I basically changed my I have no idea how this affect performance though. Also, the new interface |
Gave the libcamera fork a try, afraid it's not a viable option at the moment, even at 640x480 it completely pegs a 3B+, let alone a Zero 2. UVC uses so little CPU, even at 1080p on a NoIR v2 that I don't think raspicam will be missed. |
@alucryd Did you try https://github.com/ArduCAM/mjpg-streamer ? or something else? |
That's the one I tried, yes. |
Could you tell me what you mean by 'pegs a 3b+'? |
Something is happening causing mjpg-streamer to be compiled without the input_raspicam plugin due to unmet dependencies. If I had to guess, something changed with the location of /opt/vc/include that isn't being installed on the root image causing the plugin to have unmet dependencies. The raspi camera doesn't work out of the box because it's missing the so associated with the plugin.
The text was updated successfully, but these errors were encountered: