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

[Ingomar Wesp]

Hey!

I recently had to learn the hard way that setting
CMAKE_INCLUDE_PATH,CMAKE_LIBRARY_PATH and CMAKE_PROGRAM_PATH does not result 
in equal behavior than just setting CMAKE_PREFIX_PATH. I attempted to build 
kdebase/workspace and ran into a wall when the build system tried to link some 
plasma engine against my system wide akonadi instead of the locally installed 
one. After some help from #kde-devel, I just set CMAKE_PREFIX_PATH instead of 
the three other variables and the build went through.

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>.

Best regards,
Ingo