include build configuration information in installation (Feature #645)
| Status: | Done | Start date: | |
|---|---|---|---|
| Priority: | High | Due date: | |
| Assignee: |  Andrey Kamaev |
% Done: | 0% |
| Category: | build/install | ||
| Target version: | 2.4.0 | ||
| Difficulty: | Pull request: |
Description
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 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.
Associated revisions
#645 Added cv::getBuildInformation function (with sample) to get OpenCV build configuration
Merge pull request #645 from taka-no-me:bump_headers
History
Updated by Alexander Shishkov about 13 years ago
- Description changed from [[OpenCV]] can be built with a number of different options, and also will con... to OpenCV can be built with a number of different options, and also will configu... More
Updated by Kirill Kornyakov about 13 years ago
We should probably consider this feature for 2.4 release
- Priority changed from Normal to High
- Target version set to 2.4.0
Updated by Andrey Kamaev almost 13 years ago
The function cv::getBuildInformation() is added to opencv_core. It will be released in OpenCV 2.4.
- Status changed from Open to Done
- Assignee set to Andrey Kamaev