[Paraview] Forcing a Qt version

[Renato N. Elias]

Hi John, in my case I also tried to clean all files from my build 
directory (uncountable times) before changing Qt version, but it has not 
worked either (this screen shot was taken from one of my tries 
http://www.nacad.ufrj.br/~rnelias/paraview/qt.JPG). The only thing that 
I have not tested was the hand edition of cache files. Something 
(probably me) must have messed up my system or CMake really have a big 
problem in distinguishing between different versions of the same library 
(especially Qt).

I finally gave up in struggling with CMake and deleted the older version 
of Qt (it's easier to decide when you don't have options ;o). In fact, I 
was keeping version 4.3.4 in my machine just because I thought it were 
mandatory for ParaView 3.3.x compilation, and it's not (at least I 
haven't found any incompatibility yet).

Anyway, bug or one more weirdness of the software's world...

Renato.


John Biddiscombe wrote:
> Renato
>> by modifying my PATH before the first time I run cmake on an empty 
>> build directory.
>>   
> I think the big clue here is the "empty build directory". I use 
> multiple Qt versions and CMake is quite pathological about them. If 
> you try to switch from one version to another, you really need to wipe 
> the build directory. What I usually do is edit the cache files, by 
> doing a search replace for all paths from the old Qt and replace them 
> with the new. But even this still sometimes manages to confuse CMake 
> due to configured "other files" all over the place. To be sure you 
> really have to wipe all cache stuff and make sure the new QMake is on 
> your path before rerunning ccmake.
>
> 0.02
>
> JB
>
>