adjust paraview library paths

Version 5.5.0 was just released. Looks like the lib/ dir itself should now be part of the LD_LIBRARY_PATH.

In 5.4.x and earlier:

lib/cmake/
lib/paraview-5.4/libvtkPVCommon-pv5.4.so.1

In 5.5.0:

lib/cmake/
lib/paraview
lib/libvtkPVCommon-pv5.5.so.1

The lib/paraview-5.5 only contains a plugins directory.

In both cases used the same ./makeParaView script from ThirdParty:

./makeParaView -suffix mpipy -mpi -python -qt-5.9.3  5.4.1
./makeParaView -suffix mpipy -mpi -python -qt-5.9.3  5.5.0

Will need to check (hint @acbauer) if this change is intentional or if something went wrong with our configuration, or if there is an additional cmake parameter that we are missing.

The flattening does make some sense, since all the library names are versioned with*-pv5.5.so.1 etc, but can't really see how plain paraview, paraview-config in the lib/ directory are going to work.

@sbna @grahmatt - the catalyst function object compiles OK and runs with PV 5.5.0, just need to manual adjust the LD_LIBRARY_PATH for now.

changed the description

We did make this change in 5.5 to make it a bit easier to find PV libraries. It should also be very similar between items in the build directory and the install directory. That is,

/lib should have all of the PV libraries. The Python libraries and modules will be in slightly different locations for the build and install directories but they should get pulled in automatically anyway.

So long story short, lib/ dir itself indeed should now be part of the LD_LIBRARY_PATH.

By Andrew Bauer on 2018-04-10T20:13:02 (imported from GitLab project)

OK, good to know nothing is wrong on my side. I do wonder, however, about the paraview, pvbatch backends. Since they are also dropped directly into the lib/, won't they collide if I install an even newer paraview version with the same install prefix (eg /usr/local)?

I'm getting the following CMake errors when I run the makeParaview script with the above options. I checked out the Paraview-v5.5.0 branch before running. Do I need to set the LD_LIBRARY_PATH before I run the script? If so I'm not sure which lib/ directory to set to?

CMake Error at CMakeLists.txt:654 (include): include could not find load file:

vtkModuleAPI

CMake Error at CMakeLists.txt:655 (include): include could not find load file:

vtkModuleMacros

CMake Error at CMakeLists.txt:660 (include): include could not find load file:

vtkCompilerPlatformFlags

CMake Error at CMake/ParaViewModuleTop.cmake:44 (vtk_add_to_module_search_path): Unknown CMake command "vtk_add_to_module_search_path". Call Stack (most recent call first): CMakeLists.txt:681 (include)

-- Configuring incomplete, errors occurred!

By Matt on 2018-04-11T02:22:41 (imported from GitLab project)

A wild guess on this without looking into it a bit deeper but if you're working from a PV install directory make sure that PARAVIEW_INSTALL_DEVELOPMENT_FILES is set. I don't think you'd get this far with though if you didn't have that set. For an install directory you'll want to add <installdir>/lib to your LD_LIBRARY_PATH. If you're in the install directory, see if you have <installdir>/./lib/cmake/paraview-5.5/vtkModuleAPI.cmake.

If this isn't enough information to figure out the problem (it probably isn't), maybe we can chat tomorrow to get a fast turnaround on this issue.

By Andrew Bauer on 2018-04-11T02:48:06 (imported from GitLab project)

mentioned in commit 0249dfcff07ca05034699123760fc0c40bc20079

I just realized that this is a build of PV in the OF ecosystem. I think the issue with is that PV uses submodules for stuff like VTK so if you're getting your source code from the PV repo you'll then need to go into that directory and do git submodule update --recursive which will checkout out the submodules.

By Andrew Bauer on 2018-04-11T22:00:47 (imported from GitLab project)

The submodule command did nothing so my submodules were already updated or something else is wrong. I'm on the release branch which says that the latest version is 5.5.0 so I believe this is correct. I can't find any file or library with the name vtkModuleAPI and I don't have an install directory built yet, because cmake hasn't started to compile the code yet. Either way I added where the install directory would be to the LD_LIBRARY_PATH, but still have the same errors. Are there any dependencies that changed from 5.4 that I may be missing?

By Matt on 2018-04-11T23:55:36 (imported from GitLab project)

Could you see what's in the VTK subdirectory of the main PV directory? The vtkModuleAPI.cmake file is located at /VTK/CMake/vtkModuleAPI.cmake.

If the /VTK directory is empty then you need to do the git submodule update --recursive command from the directory. At this point I can't think of any other reason why the /VTK/CMake/vtkModuleAPI.cmake couldn't be found, but maybe I'm missing something.

By Andrew Bauer on 2018-04-12T02:00:36 (imported from GitLab project)

I needed to do "git submodule init" in the ParaView directory first then "git submodule update --recursive". Sorry new to submodules. I've usually added them separately.

Now I need to update my qt version to 5.6+ since I only have 5.5.1

By Matt on 2018-04-12T02:59:46 (imported from GitLab project)

I forgot the submodule update init part as well. If there's an option to build PV without the GUI then you won't need the QT dependncy.

By Andrew Bauer on 2018-04-12T03:17:47 (imported from GitLab project)

mentioned in commit bfa4b35d155dd1294f2f69c602fdd566870d4efa

mentioned in commit 56260882c05cee223ffa44f299d921087067e6a8

closed