Closed the-programmer closed 2 months ago
@the-programmer What generator are you intending to use for your project?
What do you have set in cmake.generator
and cmake.preferredGenerators
?
Looking at your diagnostics log, I feel pretty confident that the issue is from the same issue as #4005. We are aware of the issue and are actively trying to get a fix out.
In both cases, the generator is "empty". Both in the Workspace and User settings.
@the-programmer Oh interesting, presuming you are using kits, what is the definition of the kit you are using?
Ah, I think I know what the issue is, it's not the same scenario as #4005, but it does come from the same changes over the last release.
Context for people investigating this, I believe it's because we're adding defaults to the preferredGenerators
list but then we don't find them on PATH and so we "can't find it". We are investigating a fix.
I am not (intentionally) using kits for this.
I (did) have a kit file at C:\Users\[...]\AppData\Local\CMakeTools\cmake-tools-kits.json
but I renamed that to cmake-tools-kits.json.old
so CMake/CMake Tools doesn't detect the contents.
@the-programmer Could you test with this vsix and let me know if it resolves your issue?
The fix for this issue will be released in the next hour or so in v1.20.2.
Thanks. I'll try it on Monday.
So, I just tried the pre-release versions 1.20.2 and 1.20.3. However, both of them still select Visual Studio as the compiler. Any ideas what could be causing this? or do you need more information?
@gcampbell-msft, Since your response times are usually fast. I was wondering if you noted my last comment. (The issue isn't fixed in 1.20.3)
@the-programmer Thanks for following up. The most recent official version release should solve your issue.
The fixes in #4033 should resolve your issue. However, if they do not, please open a new issue so that we can properly track it. Thanks.
Brief Issue Summary
This is a follow-up of https://github.com/microsoft/vscode-cmake-tools/issues/4018. In my
CMakeLists.txt
I have the following lineset(CMAKE_TOOLCHAIN_FILE ${CMAKE_SOURCE_DIR}/cmake/arm_none_eabi_gcc.cmake)
. This is done so CMake selects the correct compiler for cross-compiling.However it seems that a change in 1.19.49 breaks the cross compile. In version 1.19.49 CMake Tools selects the Visual studio 17 C compiler instead of my toolchain.
My toolchain is attached. (The tool "arm-none-eabi-dump" is something internal) arm_none_eabi_gcc.cmake
My CMakeLists.txt is also attached. CMakeLists.txt
CMake Tools Diagnostics
Diagnostics of 1.19.49
Diagnostics of 1.18.44
Debug Log
The Trace rebuild log from 1.19.49
And from 1.18.44
Additional Information
The only thing is that I currently don't have the time to make a full demo project that can show the issue. If required, I'll try to create it but I hope that this is sufficiënt.