The exceptions are FindOIS.cmake which I guess is used for finding OIS for the samples but which could also be useful for other projects and FindOGRE.cmake which is a strange (and recommended against by CMake devs) thing to install alongside OGRE given that if one can find that file at all then you already know OGRE is installed.
The correct course of action here would be to make those two files available as part of the 'SDK' but not install them alongside the libraries. These could be available in the documentation folder, on the website, just in the current location in the source distribution or even better, passed upstream to CMake so that everyone can benefit.
You may think that this just makes it harder for cmake-based projects to find OGRE if they have to go off trying to find where FindOGRE.cmake is and include it in their projects but let me explain how dependency finding is supposed to work in CMake...
Let's say I have a game which uses CMake to build it and has OGRE as a dependency. At build time I need to be able to find OGRE. There are two possible scenarios:
- If OGRE was not a CMake-based project then I would have to write (or download from a 3rd party) a FindOGRE.cmake file which contains logic for finding where OGRE is installed to on the system. Then calling FIND_PROJECT(OGRE) within my build system would run the file and find OGRE for me. This file would exist purely within the build system and would not be installed.
- The second scenario (which is our case) is when OGRE is a CMake-based project. In this case, OGRE is supposed to write a small CMake description file (called OGREConfig.cmake) which set variables for use in a dependee's build-system and install this file to a standard location (usually <prefix>/share/cmake/OGREConfig.cmake on Linux) in much the same way that pkg-config works. Then, when I run FIND_PROJECT(OGRE) it will automatically go looking for OGREConfig.cmake (if it can't find it, I can always give it hints e.g. for non-standard install locations) and use that to tell me where OGRE is. You can still do version checking and the like using this system.
There is documentation for all this on the CMake wiki and in the find_package() documentation.