Persistency of the cmake options is not always good

[Alexander Neundorf]

Am Dienstag 04 Juli 2006 20:32 schrieb Albert Astals Cid:
> There's a big problem [IMHO] with the fact that cmake has a cache to
> remember things because:
>
> a) You run cmake and it tells you it could not find qt4
> b) You fix your qmake to say really where it is installed
> c) You run cmake again and it still tels you it could not find qt4
> d) You rm -rf * the build dir and cmake again and it works

I'll fix this.
It shouldn't go in the cache as valid if a wrong one has been found.

> You can see that is pretty non optimal for a newcomer, as when reaching c)
> he will think that has not fixed the problem
>
> Another example:
>
> a) You run cmake on okular
> b) it tells you the pdf plugin will not be compiled because you miss
> poppler c) You install poppler and run cmake again
> d) You still get the pdf plugin will not be compiled message

This also should not happen.
If something hasn't been found, the value should be set to FOO-NOTFOUND which 
causes cmake on the next run to check again.
If this isn't the case then there's something wrong.

Alex