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,107
    • Issues 4,107
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 19
    • Merge requests 19
  • 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
  • #17083
Closed
Open
Issue created Jul 19, 2017 by mick-p1982@mick-p1982

cmake-gui makes CMakeCache.txt before a menu is presented (How to set -std=gnu++11?)

cmake-gui is nice, it gives you browsing buttons. But as damn near as I can tell, it only actually runs cmake one time.... and it does so before it's possible to see a menu or configure anything??? Am I stupid, or is cmake-gui stupid?

Why is there not an option to always regenerate CMakeCache.txt, and why is that not the default?

Consider, how does a user set the C++ standard? If it's set after Configure, then the Makefile ignores the setting if it's based on something in CMakeCache.txt. Like in my case, a check for the existence of C++'s nullptr.

Edited Jul 20, 2017 by mick-p1982
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking