Skip to content
GitLab
  • Menu
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 3,872
    • Issues 3,872
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 21
    • Merge requests 21
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & 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
  • CMake
  • CMakeCMake
  • Issues
  • #17451
Closed
Open
Created Nov 09, 2017 by Armen Levonian@alevonian

Cannot generate 64 bit configuration for Visual Studio 2017 with host=x64

CMake version: 3.10.0-rc3

Even though I specify 'host=x64' at the time of creating the configuration, I can see CMake use cl.exe from:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.11.25503\bin\Hostx64\x86

However, Visual studio 2017 has another cl.exe in:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.11.25503\bin\Hostx64\x64

When the configuration is generated, there is still only the Win32 option where the target in the linker options is still /MACHINE:X86.

What makes things worse, is that even when using Visual Studio to create a new x64 configuration from the Win32, there are still problems because CMake injects a hard-coded "%(AdditionalOptions) /machine:X86" for the "Additional Options" in the linker, thus causing the builds to fails for every project (in a complex system this can be in the hundreds of sub-projects) with the errors of conflicts specifying both x86 and x64 targets.

I do not know if this was an issue in VS 2015 as I no longer use that. I also do not know if this is an issue in the community version.

Edited Nov 09, 2017 by Armen Levonian
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking