Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong cmake generator when selecting "Visual Studio Community 2017 - amd64" kit #682

Closed
atrantan opened this issue May 11, 2019 · 6 comments
Milestone

Comments

@atrantan
Copy link

atrantan commented May 11, 2019

Brief Issue Summary

When I'm trying to switch to the Visual Studio Community 2017 - amd64 kit the chosen generator is Visual Studio 15 2017 but should be Visual Studio 15 2017 Win64

Expected:

[driver] Switching to kit: Visual Studio Community 2017 - amd64
[cms-client] Configuring using the "Visual Studio 15 2017 Win64" CMake generator

Apparent Behavior:

[driver] Switching to kit: Visual Studio Community 2017 - amd64
[cms-client] Configuring using the "Visual Studio 15 2017" CMake generator

Developer Tools Log

<!-- Paste the log contents HERE -->

Platform and Versions

  • Operating System: Windows
  • CMake Version: 3.12.1
  • VSCode Version: 1.33.1
  • CMake Tools Extension Version: 1.1.3
  • Compiler/Toolchain: Visual Studio 15 2017 Win64

Other Notes/Information

@KoeMai KoeMai added the bug a bug in the product label May 15, 2019
KoeMai added a commit to KoeMai/vscode-cmake-tools that referenced this issue May 15, 2019
Fix the wrong selection of prefered generator on 64bit builds
with visual studio.
@KoeMai
Copy link
Contributor

KoeMai commented Jun 7, 2019

I created a patchset. But after some later tests I saw that this is not the right solution ->closed it without merge. The cmake generator for Visual Studio supports architecture and toolset arguments, see at the cmake documentation. The extension already use them.

What do you mean with it nothing happens?
How does your selected kit from the kit-file looks like?

@atrantan
Copy link
Author

atrantan commented Jun 8, 2019

@KoeMai Sorry, I have updated the issue to clarify the behaviour

@atrantan
Copy link
Author

atrantan commented Jun 8, 2019

@KoeMai for the moment, and to make it work, I need to

  • explicitely type the command before opening the source folder with vscode
cmake ../ -G "Visual Studio 15 2017 Win64"
  • ... then open the folder

@KoeMai
Copy link
Contributor

KoeMai commented Jun 8, 2019

If you run the cmake configuration step inside vscode. How does your kit file looks like?

@atrantan
Copy link
Author

@KoeMai Do you mean the CMakeCache file?

@andreeis
Copy link
Contributor

We fixed this for CMake Tools 1.4, but slightly different. We are passing the platform attribute of the kit generator instead of passing the architecture in the generator name.
Closing as duplicate of #964.

@github-actions github-actions bot locked and limited conversation to collaborators Jan 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants