[Cmake] Another gripe about CMake

[Ken Martin]

Hello Matt,

To clarify this, cmake::AddCMakePaths finds where the modules are
located. To do this it looks for a file it knows to be in the Modules
directory. It just happens to be FindVTK.cmake, but we could have picked
any file. CMake doesn't actually load that file, it just looks for it to
see if it really has found the Modules directory.

Ken

> -----Original Message-----
> From: cmake-admin at public.kitware.com [mailto:cmake-
> admin at public.kitware.com] On Behalf Of William A. Hoffman
> Sent: Tuesday, December 10, 2002 10:32 PM
> To: Mathieu Mazerolle; cmake at public.kitware.com
> Subject: Re: [Cmake] Another gripe about CMake
> 
> CMake has a Modules directory with some files like FindVTK,
FindOpenGL,
> etc.
> However, unless your project includes them, cmake does not
automatically
> include
> any of those modules.   Some modules that are part of the cmake
process
> are
> automatically
> included, but nothing to do with VTK or any other specific project.
> 
> -Bill
> 
> 
> At 08:20 PM 12/10/2002 -0500, Mathieu Mazerolle wrote:
> >Hello,
> >I was also wondering why CMake has hard-coded directives to load
> >FindVTK.cmake (cmake::AddCMakePaths)? I want to run CMake bare,
without
> any
> >modules if possible, and certainly not with anything that has to do
with
> >VTK.
> >
> >-- Matt
> >_______________________________________________
> >Cmake mailing list
> >Cmake at public.kitware.com
> >http://public.kitware.com/mailman/listinfo/cmake
> 
> 
> 
> _______________________________________________
> Cmake mailing list
> Cmake at public.kitware.com
> http://public.kitware.com/mailman/listinfo/cmake