Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • CMake CMake
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4,105
    • Issues 4,105
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CMakeCMake
  • CMakeCMake
  • Issues
  • #19374
Closed
Open
Issue created Jun 12, 2019 by Craig Scott@craig.scottMaintainer

Version-specific name of qch file in packages is inconvenient

The .qch file that we currently include in packages has a version-specific name like CMake-3145.qch. When using tools like Qt Creator, you can point it at this .qch file and get nice docs directly integrated into the IDE. Unfortunately, when you update CMake, you lose the link to the .qch file because the file name changes, so you then have to go and setup the documentation again. This will be particularly annoying for users of the upcoming CMake snap, since updates will typically be enabled by default, so documentation could appear to suddenly stop working without warning whenever an update is performed in the background.

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