Vscode-cpptools: Include file not found in include directory

Created on 26 Oct 2016  路  14Comments  路  Source: microsoft/vscode-cpptools

Can't include boost header.
vs code: 1.6.1
cpptools: 0.9.2
os: macOS 10.12.1
boost:1.62 (install by brew)
vscode

Language Service bug

Most helpful comment

Another hint for people suffering from this: I accidentally had both the "C/C++", and the "C++ Intellisense" extensions installed. Disabling the latter fixed it for me.

All 14 comments

I also met the problem, do you fix it?
2016-11-13 21-36-51

No, Still waiting

I fixed it, the error in my VSCode was from "C/C++ Clang", not from the plugin

Can you tell me what you did

My error was from the plugin, "C/C++ Clang". I think yours is from "C/C++", you can install "C/C++ Clang" to help you complete codes and check, but it can't help you peek definition or go to definition.

find feference disappear, don't have loading prompt and this bug still here...

Do you have the C/C++ extension installed? Is the platform text red in the bottom right?

2016-12-29 22 08 16
2016-12-29 22 02 44
2016-12-29 21 58 35
2016-12-29 21 57 07
2016-12-29 21 55 51
@sean-mcmanus

Thanks for reporting these issues. Autocomplete for headers inside #include doesn't work currently. The goto definition for extensionless headers uses a fixed list and "boost" is not in that list (string is). We'll investigate fixing these issues later.

Another hint for people suffering from this: I accidentally had both the "C/C++", and the "C++ Intellisense" extensions installed. Disabling the latter fixed it for me.

I can confirm this answer. I had C++ Intellisense installed too, but disabled. Uninstalling solved it though!

Yes, we fixed it so extensionless headers can be found and go to definition from the header should open the file and associate it with C++ (autocomplete and quickinfo in #include still doesn't work well).

These issues should be fixed in the latest version of the extension. Please let us know if they are not.

I have the same problem with the version 0.11.0. I simply add the same path to 'browse/path' and the error message disappear. So I think this problem is caused by undefined browse path.
I do not know the root cause. It just gets rid of the ignoring message. Hope it could help others with similar problem.

Was this page helpful?
0 / 5 - 0 ratings