Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
CMake
CMake
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,229
    • Issues 3,229
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 12
    • Merge Requests 12
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • External Wiki
    • External Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CMake
  • CMakeCMake
  • Issues
  • #21851

Closed
Open
Opened Feb 22, 2021 by Craig Scott@craig.scottMaintainer

CMake's autogen triggers warning for CMP0116

With a trivial Qt project that uses AUTOMOC in a subdirectory, the policy warning for CMP0116 gets triggered by the autogen code. After inserting a bit of debugging output (because the policy warning doesn't tell you what target or dependency triggers the warning), it is being triggered when the depfile is <targetName>_autogen/deps and the customStep will be timestamp-<someHash> (depfile and customStep refer to variables in cmLocalNinjaGenerator.cxx around here).

CMake's autogen should be able to construct the Ninja dependencies without triggering CMP0116.

Cc: @kyle.edwards

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
3.20.0
Milestone
3.20.0
Assign milestone
Time tracking
None
Due date
None
Reference: cmake/cmake#21851