-
Notifications
You must be signed in to change notification settings - Fork 463
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
[1.4.0-beta] VS environment not set correctly #1243
Comments
Confirmed. We'll fix this before releasing 1.4.0
|
same issue
|
This fix is available in CMake Tools #1.4.0 which has been released. |
I am still having this issue with 1.4.0, downgrading to 1.3.1 fixes it. |
Still having the same issue, launching VS Code from VS command prompt fixes it |
You shouldn't need to launch from the VS command prompt, but it's good that's a temporary workaround. |
I'm also having issues with 1.4.0 of the |
@benvanik, please let me know the following: what kit you are using (which VS exactly, which host-target platforms), do you set any generator explicitly in settings. Please share the contents of your kits file right after migration (only the VS section is fine, no need to include anything else). Then, are you able to get unblocked with using 1.4.0 after deleting the build folder, reload project and rescanning kits? Do this after you paste us the kits content. |
This should be fixed in CMake Tools 1.4.1 which was published today. |
@andreeis Now it initializes a correct cross-compiler for MSVC CMake generator, but there is an issue.
If you have
"cmake.preferredGenerators": ["Ninja"],
in global settings - CMake-Tools'll never initializevcvarsall.bat
. It's a bit unexpected. Shouldn't it initialize a correct environment anyway if bothvisualStudio
andvisualStudioArchitecture
are present as per documentation?Originally posted by @Minimonium in #1084 (comment)
The text was updated successfully, but these errors were encountered: