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
  • #16504
Closed
Open
Issue created Dec 14, 2016 by Braden McDaniel@bradenContributor

CMAKE_CL_64 documentation error

The documentation for the CMAKE_CL_64 variable states:

Set to true when using the 64-bit cl compiler from Microsoft.

This appears to be inaccurate in a couple of respects.

  1. The value is either 1 or 0; never true. (I appreciate that CMake treats both 1 and true as logically true values; however, if this value is substituted somewhere that is not processed by CMake, the difference is material.)
  2. The value is still 0 if one is using the 64-bit compiler to build 32-bit binaries. Similarly, the value is 1 if one is using the 32-bit compiler to build 64-bit binaries. In other words, the value changes based on whether one is building 64- or 32-bit binaries, not based on whether the compiler is a 64- or 32-bit application.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking