Add OpenCVConfig.cmake files to win-superpack (Feature #1347)

Added by Daniel Takacs over 13 years ago. Updated almost 13 years ago.

Status:Done Start date:
Priority:Low Due date:
Assignee:Alexander Shishkov % Done:

0%
Category:build/install
Target version:2.4.0
Difficulty: Pull request:

Description

Now the win-superpack package came without OpenCVConfig.cmake files, so the users can't use the find_package command in their cmake based projects.
It wold be good if the superpack could contain one OpenCVConfig.cmake for every build configuration.

History

#1
Updated by Alexander Shishkov about 13 years ago

  • Description changed from Now the win-superpack package came without [[OpenCVConfig]].cmake files, so t... to Now the win-superpack package came without OpenCVConfig.cmake files, so the u... More

#2
Updated by Alexander Shishkov almost 13 years ago

  • Target version deleted ()

#3
Updated by Alexander Shishkov almost 13 years ago

  • Priority changed from High to Low

#4
Updated by Sergiu Dotenco almost 13 years ago

It should be noted that the currently provided OpenCVConfig.cmake is pretty fragile and particularly doesn't work with Windows super-pack binaries without copying these files to the bin sub-directory. For this reason I rolled my own FindOpenCV.cmake which works with all kind of directory layouts used by OpenCV on major platforms.

Nevertheless, for a proper OpenCVConfig.cmake it might help to follow the instructions provided at http://www.vtk.org/Wiki/CMake/Tutorials/How_to_create_a_ProjectConfig.cmake_file.

#5
Updated by Alexander Shishkov almost 13 years ago

  • Assignee deleted (Vadim Pisarevsky)

#6
Updated by Alexander Shishkov almost 13 years ago

  • Target version deleted ()

#7
Updated by Andrey Kamaev almost 13 years ago

  • Status changed from Open to Done
  • Target version set to 2.4.0
  • Assignee set to Alexander Shishkov

#8
Updated by Daniel Takacs almost 13 years ago

Sergiu Dotenco wrote:

It should be noted that the currently provided OpenCVConfig.cmake is pretty fragile and particularly doesn't work with Windows super-pack binaries without copying these files to the bin sub-directory. For this reason I rolled my own FindOpenCV.cmake which works with all kind of directory layouts used by OpenCV on major platforms.

Nevertheless, for a proper OpenCVConfig.cmake it might help to follow the instructions provided at http://www.vtk.org/Wiki/CMake/Tutorials/How_to_create_a_ProjectConfig.cmake_file.

That's really great, and if it's cross platform, I think it should be part of CMake. I'm not sure what is their policy, but to me it looks like most of the scripts in Modules are made by 3rd party developers.

Also available in: Atom PDF