[Paraview] Support for QT5 broken with qt 5.3.X?

[B.W.H. van Beest]

Could it be that the support for Qt 5.3.x is broken in Paraview?

When I upgraded from Qt5.2.1 to Qt5.3.1 recompiled paraview, I always
get link errors as described below.
On inspection, I noticed that symbols like

'qt_filedialog_existing_directory_hook' are no longer found in Qt5.3.1, whereas they still are there in Qt5.2.1.
I don't know how how ParaView implicitly uses these symbols, perhaps knows more on this.

Kind Regadds,
Bertwim 






On 08/07/2014 12:00 PM, Huebl, Axel wrote:
> Hm, looks like the cleanest way to get it running is to remove default
> installations of qt from the system path(s) and to specificity only one
> specific installation via environment flags.
>
> (I am suggesting something that can be achieved with a module system,
> e.g. on a cluster)
>
> Alternatively you can try to scratch all the advanced flags together
> that are still wrong and set them by hand.
>
>> What does this tell me?
> Yep, but basically it is still an environment problem.
>
> Best,
> Axel
>
> On 07.08.2014 03:05, B.W.H. van Beest wrote:
>> Hi Axel,
>>
>> setting CMAKE_PREFIX_PATH does not make a difference. The  special
>> variables left that have a reference to the wrong qt installation are
>> QT_QT3SUPPORT_LIBRARY and QT3SUPPORT_LIBRARY_RELEASE variables.  Qt5
>> does no longer provide Qt4 support .
>>
>> Also QT_QTCORE_LIBRARY and QT_QDBUS and QT_GUI_LIBRARY_  are wrong ....
>> The correspinding HEADER-varinant are ok, though.
>> What does this tell me?
>>
>> Regards,
>> Bertwim
>>
>>
>> On 08/06/2014 11:34 AM, Huebl, Axel wrote:
>>> Dear Bertwim,
>>>
>>>
>>> good to hear that.
>>>
>>> sorry - CMAKE_PREFIX_PATH is an environment variable like "PATH" and
>>> "LD_LIBRARY_PATH" to hint install directories to CMake modules.
>>>
>>> The compile error still looks like something got mixed - can you try
>>> again with the CMAKE_PREFIX_PATH hint?
>>> Did you verify all "advanced" variables set from the FindQt module with
>>> ccmake?
>>>
>>>
>>> Best,
>>> Axel
>>>
>>> On 05.08.2014 21:37, B.W.H. van Beest wrote:
>>>> 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
>>>>
>>
>>