Comments (11)
Are you trying to compile with cl.exe? Did you run CMake: Configure? When you run C/C++: Log Diagnostics with a C++ file active what is the output in regards to system includes?
from vscode-cmake-tools.
Here is my configuration result, but it didn't work
[proc] Run the command D:\QT6\Tools\CMake_64\bin\cmake.exe --version
[proc] Run D:\QT6\Tools\CMake_64\bin\cmake.exe -E capabilities
[variant] A new set of variables is loaded
[kit] successfully loaded 15 toolkits from C:\Users\sj2003\AppData\Local\CMakeTools\cmake-tools-kits.json
[proc] Run the chcp command
[visual-studio] is patched from D:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat C:\Program Files (x86)\Windows Kits\10\bin\x64 to C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x64 Windows SDK path
[main] Configuring the project: videoCall
[proc] Run the following command: D:\QT6\Tools\CMake_64\bin\cmake.exe --no-warn-unused-cli -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -SC:/Users/sj2003/Desktop/videoCall -Bc:/Users/sj2003/Desktop/videoCall/build -G "Visual Studio 17 2022" -T host=x64 -A x64
[cmake] Not searching for unused variables given on the command line.
[cmake] -- Selecting Windows SDK version 10.0.22621.0 to target Windows 10.0.19045.
[cmake] -- The CXX compiler identification is MSVC 19.40.33811.0
[cmake] -- Detecting CXX compiler ABI info
[cmake] -- Detecting CXX compiler ABI info - done
[cmake] -- Check for working CXX compiler: D: / Program Files/Microsoft Visual Studio / 2022 / Community/VC/Tools/MSVC / 14.40.33807 / bin/Hostx64 / x64 / cl. Exe - skipped
[cmake] -- Detecting CXX compile features
[cmake] -- Detecting CXX compile features - done
[cmake] -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
[cmake] -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
[cmake] -- Looking for pthread_create in pthreads
[cmake] -- Looking for pthread_create in pthreads - not found
[cmake] -- Looking for pthread_create in pthread
[cmake] -- Looking for pthread_create in pthread - not found
[cmake] -- Found Threads: TRUE
[cmake] -- Performing Test HAVE_STDATOMIC
[cmake] -- Performing Test HAVE_STDATOMIC - Success
[cmake] -- Found WrapAtomic: TRUE
[cmake] -- Could NOT find WrapVulkanHeaders (missing: Vulkan_INCLUDE_DIR)
[cmake] -- Configuring done
[cmake] -- Generating done
[cmake] -- Build files have been written to: C:/Users/sj2003/Desktop/videoCall/build
[visual-studio] is patched from D:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat C:\Program Files (x86)\Windows Kits\10\bin\x64 to C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x64 Windows SDK path
from vscode-cmake-tools.
@shawn1j Yeah, can you check the C/C++: Log Diagnostics output with a C/C++ file active?
Or if you set C_Cpp.loggingLevel to "Debug" and check the "C/C++" logging for message "Custom configurations received:" that will show what receive from the CMake Tools extension after opening a file.
from vscode-cmake-tools.
This is my c/c + + log output (because there is too much content, I stored it in the file):
from vscode-cmake-tools.
This is my cmake output
from vscode-cmake-tools.
@shawn1j Your logging indicates CMake Tools is not sending us any configuration info for the header files that are opened, i.e. it doesn't appear that you're configured correctl or it could be a CMake Tools issue.
from vscode-cmake-tools.
@shawn1j Thank you for reporting this issue. Regarding this issue, we tried to reproduce this issue using a simple demo project however we were unable to reproduce this issue for you. In order to investigate further, please provide us with a simple demo project to reproduce the issue and we look forward to your feedback.
from vscode-cmake-tools.
Of course, here's my case, and it's very simple.
CMakeLists.txt
cmake_minimum_required(VERSION 3.10)
project(demo LANGUAGES CXX)
set(CMAKE_CXX_STANDARD 20)
set(CMAKE_CXX_STANDARD_REQUIRED True)
set(CMAKE_INCLUDE_CURRENT_DIR ON)
add_executable(demo main.cpp )
main.cpp
#include <iostream>
int main(int argc, char **argv)
{
std::cout << "Hello World" << std::endl;
return 0;
}
The following is the output of cmake-tools, because c/ C ++ output too much information, I put it in the c_cpp.logging.txt file.
c_cpp.logging.txt
[proc] Executing command: D:\QT6\Tools\CMake_64\bin\cmake.exe --version
[proc] Executing command: D:\QT6\Tools\CMake_64\bin\cmake.exe -E capabilities
[variant] Loaded new set of variants
[kit] Successfully loaded 9 kits from C:\Users\sj2003\AppData\Local\CMakeTools\cmake-tools-kits.json
[proc] Executing command: chcp
[visual-studio] Patch Windows SDK path from C:\Program Files (x86)\Windows Kits\10\bin\x64 to C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x64 for D:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat
[main] Configuring project: src
[proc] Executing command: D:\QT6\Tools\CMake_64\bin\cmake.exe --no-warn-unused-cli -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -SC:/Users/sj2003/Desktop/demo/src -Bc:/Users/sj2003/Desktop/demo/src/build -G "Visual Studio 17 2022" -T host=x64 -A x64
[cmake] Not searching for unused variables given on the command line.
[cmake] -- Selecting Windows SDK version 10.0.22621.0 to target Windows 10.0.19045.
[cmake] -- The CXX compiler identification is MSVC 19.40.33811.0
[cmake] -- Detecting CXX compiler ABI info
[cmake] -- Detecting CXX compiler ABI info - done
[cmake] -- Check for working CXX compiler: D:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.40.33807/bin/Hostx64/x64/cl.exe - skipped
[cmake] -- Detecting CXX compile features
[cmake] -- Detecting CXX compile features - done
[cmake] -- Configuring done
[cmake] -- Generating done
[cmake] -- Build files have been written to: C:/Users/sj2003/Desktop/demo/src/build
[visual-studio] Patch Windows SDK path from C:\Program Files (x86)\Windows Kits\10\bin\x64 to C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x64 for D:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsall.bat
Environment
- OS and Version: windows 10 x64
- VS Code Version: 1.90
- C/C++ Extension Version: 1.20.5
- CMake Version: 3.24.2
- Visual Studio 2022 Version: v17.10.1
from vscode-cmake-tools.
@shawn1j I'm very sorry, I don't get this error with the code you provided, can you give me some advice?
from vscode-cmake-tools.
Sorry to keep you waiting, I tried to use the latest version of cmake (version 3.29.6). After my testing, I found that when I used Visual Studio 2022 Developer Command Prompt v17.10.1 to launch vs code, vs code intellisense will work properly. This did not work with cmake (version 3.24.2), which I used earlier.
Here is the effect of starting vs code without Visual Studio 2022 Developer Command Prompt v17.10.1.
I wonder if this has anything to do with my computer environment. can you give me some advice?
from vscode-cmake-tools.
@shawn1j When I start vscode without Visual Studio 2022 Developer Command Prompt I get a generator not found, which should be normal because my generator is installed by installing VS and not separately, but I still can't reproduce the problem you described.
from vscode-cmake-tools.
Related Issues (20)
- CMake configure preset installDir setting is evaluated relative to the binary directory instead of the source directory HOT 6
- [Loc] Property’s tooltip info in file "CMakePresets.json" is not localized
- [Flaky]Duplicate information appeared in output when Add CMakePreset.json
- copyCompileCommands to the original path still leaves a corrupted CDB on Windows HOT 2
- "CMake: build" is repeated twice in the list
- in vscode, How to use v141 toolset in VS2022 with cmake HOT 6
- Double-clicking on one of a target's "References" does nothing HOT 4
- Project outline does not show sources of custom targets with commands HOT 5
- Failure to ask the user to select a kit due to erroneously not finding CMakeLists.txt HOT 1
- Failed to set up project in a subfolder of a git repository HOT 7
- Debugging fails on macOS HOT 7
- [FR] Support module map files HOT 1
- setting active project again after quick start causes second configure
- Include paths are wrong on macOS case sensitive filesystems HOT 7
- test issue
- VSCode CTest Google Test complains non-existing `DartConfiguration.tcl` HOT 5
- cmake.buildBeforeRun is not working as expected HOT 3
- Launch Target doesn't initialise the shell as per the user's config
- Configure on Windows generates a faulty project HOT 1
- Add toolset telemetry point for presets
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vscode-cmake-tools.