[Vxl-maintainers] our local CMake modules directory

[Ian S. <ian...@st...>]

Hi,

Summary:
Let's tidy up the config.cmake/Modules directory. Amitha and I have write
access to the CMake repository, where we can put much of the extra
functionality in our own Modules directory.


Detailed:

Why do we have lots of extra FindXXX.cmake files in config.cmake/Modules
that don't really do anything VXL specific?

In particular I'm thinking of FindQT.cmake, FindMPEG.cmake,
FindNativeJPEG.cmake, etc.

It appears to me that
1. these files either contain unnecessary functionality
e.g FindMPEG.cmake merely appears to replicate HAS_MPEG, MPEG_INCLUDE_PATH
with HAS_NATIVE_MPEG, NATIVE_MPEG_INCLUDE_PATH)
or
2. The functionality in them would be better move to CMake's own modules
directory.
e.g FindQT.cmake does useful stuff like figures out which other libraries
are need by qt.
Having our own FindQT.cmake is particularly inappropriate since we don't
have any qt code in the vxl repository.

I got to thinking about this because CMake is now powerful enough that we
don't have to use the complex and unpleasant CMakeListsLink.txt files
anymore (thanks Amitha.) In a similar vien, the more powerful ability to use
CMake variables should now mean that we do not need to use so many of our
own .cmake files.

Since CMake is now on a release schedule, we can't can't do this properly
until the next release. But I think it is worth starting now.

Ian.