-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-English gcc querying doesn't work #4542
Comments
If compile_commands.json is valid, the extension will use the info from compile_commands.json to determine system includes instead of the values from includePath (see https://code.visualstudio.com/docs/cpp/customize-default-settings-cpp#_system-include-pathdefines-resolution-strategies). Can you try adding |
@michelleangela I try adding -i /usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include to compile_commands.json but it doesn't work |
You shouldn't need to add system include paths when |
To clarify, please share the output of |
IntelliSense Engine = Default. |
@xspeed1989 That is not the correct logging -- the logging shows no IntelliSense info. Can you run the C/C++: Log Diagnostics command with a relevant source file active? |
Also, if you're using CMake, then you probably shouldn't be using compile_commands.json -- you should set your configurationProvider setting to "vector-of-bool.cmake-tools". |
@sean-mcmanus |
Look at the bottom of vs code, in Chinese mode, it is like this maybe it isn't caused by different language |
The --gnu_version=80100 appears to be incorrect (80100 is our default if we fail to read the version from the defines). Can you enable debug logging: https://code.visualstudio.com/docs/cpp/enable-logging-cpp ? And see if the defines are output for the compiler (e.g. "define: GNUC=9"). We added support for handling gcc output in other languages, but it's possible there could be some issue with that. |
@sean-mcmanus
|
Querying /usr/bin/g++ is failing for some reason (not giving the output we expect). What output do you get when you run |
We've added better logging for this case (for 0.26.2 or 0.26.3). |
|
Okay, thanks for the info. Looks like our handling of non-English gcc output isn't working correctly. We have some ideas on an alternative fix. |
Thanks! |
@bobbrow I think this should be easily/quickly fixable via looking for |
If we validate paths between the |
This issue is fixed in 0.28.0. |
When i set compileCommands , it gets a green squiggly saying that it can not load one of it's dependencies and to edit the include path
it seem to be when compileCommands is set,includePath will be ignored, then i set forceinclude,but it dosn't work
the file is in /usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/include
my os is manjaro latest
The text was updated successfully, but these errors were encountered: