Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ParaView ParaView
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,962
    • Issues 1,962
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 98
    • Merge requests 98
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • 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
  • #16880
Closed
Open
Issue created Sep 07, 2016 by olesen@olesenContributor

Using '+' as list separator causes some problems building documentation.

In ParaViewMacros.cmake, ParaViewPlugins.cmake and in proxydocumentation.cmake, a plus (+) character is used to build pseudo lists, since the semi-colon (;) would otherwise cause issues in shell commands. Unfortunately, this means that if the file-system path itself contains a plus (+) character, this will be incorrectly interpreted as a list separation character. Eg, for a path such as /nfs/software/gcc-4.8+openmpi-1.10.4/foo/... would be falsely split into two parts, neither of which exist.

Changing this list-separator to a less commonly used character (eg, a comma) could help. Replacing it with an improbable multi-character sequence would likely be the more robust solution. For example, ,, or ,@, etc.

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