I understand and agree. However, that was not what I had witnessed.
“make install”, which I ran right after “cmake …” , as per installation manual, also returns errors related to alphamat, as expected Of course.
Thus, the error originally begins in the “cmake” procedure. So, it must be fixed there, instead of amending “make install” procedure.
Anyway, the fact is that after I changed the installation directory, the installation process finished successfully.
In fact that was even better , because it made me aware that having openCV 4.5 release located within user’s home directory and libraries installed within virtualenv, gives more flexibility.
So, if, in the future, we decide to run 2 releases of opencv in the same machine, we will have that flexibility.
Now, I’m going deeper in the installation parameters and how I could optimize scanning and image processing. What arguments must I add in the “cmake” procedure in order to achieve better and more optimized results, saving hardware resources. btw, it’s a Rasp Pi device.
Best wishes,
I