Updated by Alexander Shishkov about 13 years ago
OpenCV [[OpenCV]] can be built with a number of different options, and also will configure its build based on available components. Once the build occurs, it is not easy to figure out the build configuration (was it built with ffmpeg or not, etc.).
"ldd" and similar tools can be used forensically to figure out the build, but it would be much easier if the build included its configuration information. I see many users on the mailing lists struggling to figure out why OpenCV [[OpenCV]] is not working for them when it is really a build/configuration problem.
Two possibilities:
1. Include a file in the installation, such as cvconfig.h, or the captured output of the cmake configuration.
2. Include a "cvinfo" program that prints out configuration info when run. I am thinking of the sort of info that "gcc -v" prints.
"ldd" and similar tools can be used forensically to figure out the build, but it would be much easier if the build included its configuration information. I see many users on the mailing lists struggling to figure out why OpenCV [[OpenCV]] is not working for them when it is really a build/configuration problem.
Two possibilities:
1. Include a file in the installation, such as cvconfig.h, or the captured output of the cmake configuration.
2. Include a "cvinfo" program that prints out configuration info when run. I am thinking of the sort of info that "gcc -v" prints.