Replies: 1 comment 3 replies
-
You should now use Motion instead of Motionplus. I believe this issue is resolved in the current master branch of Motion. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am doing a reinstall of motionplus on an RPI4/Bookworm. I already have motionplus running on a few other RPI4's and didn't really have a problem getting it installed by following the directions on the motionplus install page. On this install, I'm running into a new set of errors on the make commnand for motionplus installs. The make ends with:
MP -MF $depbase.Tpo -c -o libcam.o libcam.cpp &&
mv -f $depbase.Tpo $depbase.Po
libcam.cpp: In member function ‘void cls_libcam::config_control_item(std::string, std::string)’:
libcam.cpp:273:32: error: ‘AeLocked’ is not a member of ‘libcamera::controls’; did you mean ‘AwbLocked’?
273 | controls.set(controls::AeLocked, mtob(pvalue));
| ^~~~~~~~
| AwbLocked
libcam.cpp:423:39: error: ‘AeState’ is not a member of ‘libcamera::controls::draft’; did you mean ‘AwbState’?
423 | controls.set(controls::draft::AeState, mtoi(pvalue));
| ^~~~~~~
| AwbState
make[2]: *** [Makefile:508: libcam.o] Error 1
make[2]: Leaving directory '/home/pi/motionplus/src'
make[1]: *** [Makefile:568: all-recursive] Error 1
make[1]: Leaving directory '/home/pi/motionplus'
make: *** [Makefile:412: all] Error 2
I;ve seen a few posts about problems with libcamera a compatibility issues with different versions of libecamera but I guess I'm just not geeky enough to understand what they are telling me. Is there something I'm missing?
Beta Was this translation helpful? Give feedback.
All reactions