Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • ParaView ParaView
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 2k
    • Issues 2k
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 83
    • Merge requests 83
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaViewParaView
  • ParaViewParaView
  • Issues
  • #19695
Closed
Open
Issue created Feb 17, 2020 by Jeff Mauldin@jamauldDeveloper

Catalyst: Node class from vtkPlotEdges.cxx name-collides with linked simulations (SPARC)

While linking ParaView/Catalyst to SPARC with a static (non-shared) build of the ParaView libraries, my link failed due to the Node class in vtkPlotEdges.cxx and vtkPlotEdges.h. The link failure was due to a name collision ("previously defined") for the class named Node. There is a class named Node in SPARC and a class named Node in vtkPlotEdges.cxx. (Both at the top-level namespace, i.e. the global namespace.)

I tried an experimental workaround which worked which was to rename the Node class to something more unique in the source code (in vtkPlotEdges.cxx and vtkPlotEdges.h). However, Node is probably a much too generic name in general, and either the class name should be permanentely changed to something less likely to collide with simulations or it should be protected in some kind of namespace or both.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking