Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 472
    • Issues 472
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #793
Closed
Open
Issue created Apr 10, 2018 by Mark OLESEN@markMaintainer

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.

Edited Apr 10, 2018 by Mark OLESEN
Assignee
Assign to
Time tracking