CMAKE_PREFIX_PATH vs. CMAKE_[INCLUDE|LIBRARY|PROGRAM]_PATH

[Alexander Neundorf]

On Friday 08 October 2010, Ingomar Wesp wrote:
> >> I don't know enough about the finer differences between setting all of
> >> the three variables as opposed to setting just CMAKE_PREFIX_PATH, but if
> >> CMAKE_INCLUDE_PATH,CMAKE_LIBRARY_PATH and CMAKE_PROGRAM_PATH are indeed
> >> obsolete and lead to failing builds, then we should definitely state
> >> that on
> >> <http://techbase.kde.org/index.php?title=Development/Tutorials/CMake>.
> >
> > IMHO, no. If anywhere it should be documented in the cmake docs. We
> > shouldn't replicate the cmake docs in our techbase.
>
> I agree. However, we probably shouldn't recommend build settings that do
> not work, either.


Yes. Using CMAKE_PREFIX_PATH is definitely recommended.
Please edit the page on techbase accordingly. It should say something like 
that the thing to do is to set up CMAKE_PREFIX_PATH, and if you really want 
to, you can also set the three separate ones (which were available also 
before cmake 2.6.0)

Alex