microsoft / microsoft/vscode-cmake-tools
CUDA target is not configured for cpptools
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 546
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 32
Description
### Brief Issue Summary
With `"configurationProvider": "vector-of-bool.cmake-tools"` working for C++ targets, CUDA targets created by `add_library` are not properly configured, CUDA headers shown as not found in IntelliSense. Adding
```
target_include_directories(mycudalib PRIVATE
${CMAKE_CUDA_TOOLKIT_INCLUDE_DIRECTORIES})
```
Doesn't solve the issue.
### Platform and Versions
Version: 1.33.1 (user setup)
Commit: 51b0b28134d51361cf996d2f0a1c698247aeabd8
Date: 2019-04-11T08:27:14.102Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.17763
Compiler/Toolchain: Visual C++ 2017
Contributor guide
Research direction
Start by reproducing the issue with configurationProvider set to vector-of-bool.cmake-tools and a CUDA target created by add_library, then inspect how CMake Tools generates cpptools configuration for that target. No source files or tests are named; done means CUDA headers are resolved in IntelliSense without relying on the ineffective target_include_directories workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp, typescript
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100