[CMake] How to work around broken Find module

[Ryan Pavlik]

If you look at my repository, I have a system set up that I call
"UseBackportedModules" - basically it checks the CMake version and
extends the CMAKE_MODULE_PATH to include only those directories
mentioning newer version than the current user's cmake version.  It
works pretty well for me.

http://github.com/rpavlik/cmake-modules/blob/master/UseBackportedModules.cmake
http://github.com/rpavlik/cmake-modules/tree/master/cmake-2.8.3-modules/
http://github.com/rpavlik/cmake-modules

Ryan

On Thu, Oct 28, 2010 at 4:00 AM, Marcel Loose <loose at astron.nl> wrote:
> Hi all,
>
> What is the best way to work around a broken Find module?
>
> A technique I've used up till now is to wrap the broken module in a
> module with the same name that I store in my own module directory. This
> way, my wrapper module will be picked up first. Problem with this
> approach is, of course, that this might break when someone is using a
> newer CMake in which the broken module has been fixed.
>
> A different approach would be to copy the fixed module from the newer
> CMake and store it in my own module directory. But this might also
> break, when newer versions of CMake are released.
>
> Any ideas?
>
> Best regards,
> Marcel Loose.
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
>



-- 
Ryan Pavlik
HCI Graduate Student
Virtual Reality Applications Center
Iowa State University

rpavlik at iastate.edu
http://academic.cleardefinition.com
Internal VRAC/HCI Site: http://tinyurl.com/rpavlik