Replies: 2 comments 1 reply
-
Hmmm... You are not doing anything wrong, it seems that the C++ extension cannot recognise the compiler installed via xpm. :-( The reason I could not detect it before is that on my test machine I had a I'll further investigate. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I created #28 to keep track of the bug. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been struggling to get IntelliSense to work correctly for the quick start example.
The build is successful but IntelliSense has errors.
The following things are working:
compile_commands.json
c_cpp_properties.json
is updated with the path forcompile_commands.json
include
directory) are indexed by IntelliSenseHowever, the system header
iostream
(line 15 in hello-world.cpp) is not found.The C/C++ extension give this output:
Unable to resolve configuration with compilerPath: "C:\Users\nic\Desktop\gcc-test\xpacks\.bin\gcc"
Any ideas about what I am doing wrong?
Environment
OS: Windows 10
xPack extension version: v0.4.16
C/C++ extension version: v1.7.1
Xpm version: 0.10.8
Node and global npm packages managed using Volta
Beta Was this translation helpful? Give feedback.
All reactions