[Paraview] Buggy development package?
Michael Wild
themiwi at gmail.com
Wed Jul 7 07:45:16 EDT 2010
Also, ParaViewConfig.cmake, VTKConfig.cmake and VTKLibraryDepends.cmake have similar problems.
When I said that unsetting the XXX_LIB_DEPENDS variables was solving the problem, I was mistaken. It actually breaks things, but I didn't notice it until tried to load the plugin (I was using -undefined dynamic_lookup ...).
Coming to think of it, shouldn't one also use the same Qt version that was used to compile ParaView? So that one should also be included in the development package, right? And on Mac the frameworks should have their install_name directory set to @executable_path/../Frameworks and the libraries to @executable_path/../Libraries. Of course, ParaViewUse.cmake should make sure that the correct Qt is discovered and used.
Michael
On 7. Jul, 2010, at 11:45 , Dave Partyka wrote:
> Good Catch Michael, I'll give that a shot
>
> On Wed, Jul 7, 2010 at 2:43 AM, Michael Wild <themiwi at gmail.com> wrote:
>
>> Hi all
>>
>> I wanted to give the new development package
>> (ParaView-Development-3.8.0-Darwin-x86_64.tar.gz) a try and use it to
>> compile a plugin on my Mac. However, it seems that
>> lib/paraview-3.8/CMake/ParaViewLibraryDepends.cmake contains XXX_LIB_DEPENDS
>> variables referencing libraries from the custom Qt installation used to
>> build the package (/Users/partyd/Dashboards/Support/qt-4.6.2-MacOSX10.5). Of
>> course, none of those Qt libraries can be found...
>>
>> As a hack I just unset the offending pqComponents_LIB_DEPENDS and
>> vtkPVServerManager_LIB_DEPENDS variables after including PARAVIEW_USE_FILE.
>> But I suspect this might fail on some operating systems.
>>
>> Currently I have no idea how this could be fixed in a good way, since these
>> entries are auto-created by CMake. Perhaps one way would be wrapping
>> TARGET_LINK_LIBRARIES in a custom function that explicitly sets the
>> LINK_INTERFACE_LIBRARIES property, replacing Qt libraries by
>> "\${QT_LIBRARIES}", suitably escaped such that it ends up as ${QT_LIBRARIES}
>> in the ParaViewLibraryDepends.cmake file, expanding to the users
>> installation of Qt when it is included.
>>
>> Michael
More information about the ParaView
mailing list