search

NVIDIA / nsight-vscode-edition

A Visual Studio Code extension for building and debugging CUDA applications.
Other
68 stars 11 forks source link

vscode output Unable to locate nvcc compiler: nvcc when developing remotely #10

Closed umiswing closed 2 years ago

umiswing commented 2 years ago

I am trying to build my remote cuda development environment with vscode and its extension. I successfully install the c/c++ and nsight-vscode-edition(in the remote machine). I successfully install the cuda toolkit and add it to the PATH in the remote machine. I can call the nvcc in the terminal remotely. But my vscode didn't give the intellisense, instead, it outputs Unable to locate nvcc compiler: nvcc or can not open some cuda header files(I guess it might be problem about path). How to fix it? Will be grateful for your help :)

My environment:

vscode Version: 1.64.2 (user setup) Commit: f80445acd5a3dadef24aa209168452a3d97cc326 Date: 2022-02-09T22:02:28.252Z Electron: 13.5.2 Chromium: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 10.0.19042 cuda 11.1 .bashrc export LD_LIBRARY_PATH=/usr/local/cuda-11.1/lib64:$LD_LIBRARY_PATH export PATH=/usr/local/cuda-11.1/bin:$PATH remote machine CentOS Linux 7 local machine windows 10

umiswing commented 2 years ago

Fix it! I read https://docs.nvidia.com/nsight-visual-studio-code-edition/release-notes/index.html and find using cuda 11.3 is better. By the way, I find I turn off the IntelliSense... In the end, I turn on the IntelliSense and install the cuda 11.3. Now it works well. :)