[Paraview] what if you have two qt-installations?

[B.W.H. van Beest]

Dear Axel,

No I haven't. To follow-up on your suggestion, I ran ccmake again to set
this parameter. No CMAKE_PREFIX_PATH is in the list!
What I did try -and what did make a difference, was not only prepending
the path to qt5/lib to  LD_LIBRARY_PATH, but also ensuring that qt/bin
was first in $PATH.  This indeed has the result that all libQt5
directories found were the correct ones.  Maybe that amounts to the same?

However, Now I have a different compile error:

CMakeFiles/QtTesting.dir/pqNativeFileDialogEventPlayer.cxx.o: In
function `pqNativeFileDialogEventPlayer::start()':
pqNativeFileDialogEventPlayer.cxx:(.text+0x263): undefined reference to
`qt_filedialog_existing_directory_hook'
pqNativeFileDialogEventPlayer.cxx:(.text+0x285): undefined reference to
`qt_filedialog_open_filename_hook'
pqNativeFileDialogEventPlayer.cxx:(.text+0x2a7): undefined reference to
`qt_filedialog_open_filenames_hook'
pqNativeFileDialogEventPlayer.cxx:(.text+0x2b4): undefined reference to
`qt_filedialog_save_filename_hook'
CMakeFiles/QtTesting.dir/pqNativeFileDialogEventPlayer.cxx.o: In
function `pqNativeFileDialogEventPlayer::stop()':


etc.

Any ideas?






On 08/05/2014 08:38 PM, Huebl, Axel wrote:
> Dear Bertwim,
>
> have you tried prepending/setting the
>   CMAKE_PREFIX_PATH
>
> to your qt5 install dir?
>
> Best,
> Axel
> On 05.08.2014 18:07, B.W.H. van Beest wrote:
>> Hi Burien, thanks for responding.
>>
>> I have done you suggested, but to no avail.
>> Somehow, the path to the executable qmake is not sufficient to determine
>> all the other QT5 libraries.
>> Having said that, in one of the by now many attempts to get paraview
>> configured, I found that indeed the correct QT5 libraries were selected.
>> That build, however failed (missing symbol, cannot remember which one).
>> In trying to correct this is, the wrong QT5 libraries were selected by
>> ccmake. I just cannot figure out how this cmake thing works, or what I
>> can do to force it.
>> Any suggestions?
>>
>> Kind Regards,
>> Bertwim
>>
>>
>>  
>> On 08/04/2014 10:04 PM, Burlen Loring wrote:
>>> system install may be first in the linker search path. have you
>>> checked? If that's it: rm your build, and in addition to
>>> QT_QMAKE_EXECUTABLE, prepend & export your qt install paths to
>>> LD_LIBRARY_PATH and PATH before you run cmake. Each time when you run
>>> PV do the same.
>>>
>>> On 08/04/2014 12:01 PM, B.W.H. van Beest wrote:
>>>> Hello,
>>>>
>>>> On my system, I have 2 installations of QT5. One is the distribution
>>>> that comes with my linux distribution (qt5.1.1.openSuSe 13.1), the other
>>>> one is a more recent version (5.3.1), which I downloaded and installed
>>>> in a different location.
>>>> Using ccmake, setting the QT version to 5, as well as setting
>>>> QT_QMAKE_EXECUTABLE to qmake of the new location,
>>>> I still see that ccmake selects of number of qt5-libraries that belong
>>>> to the old SUSE-distribution, (e.g. libQt5Declarative.so, but many more,
>>>> in fact).  I can build paraview, though, and it even seems to work
>>>> (smoketest), but at program exit it segfaults.
>>>>
>>>> I wonder how I can tell cmake to configure for 1 qt version. Surely, I
>>>> don't need to change all the entries by hand?
>>>>
>>>> Thanks in advance
>>>> Bertwim