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

[Ingomar Wesp]

Alexander Neundorf wrote:

> On Friday 08 October 2010, Ingomar Wesp wrote:
>> 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)

Will do.

If FindAkonadi.cmake is the only culprit, it would certainly be nice if 
someone could fix it as well - that is, if we still aim to support more exotic 
install hierarchies. Unfortunately, I currently don't have the necessary 
knowledge to do that …