Skip to content
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

Wrong includePath when indexing intellisense #1154

Closed
guettomusick opened this issue Oct 31, 2017 · 4 comments
Closed

Wrong includePath when indexing intellisense #1154

guettomusick opened this issue Oct 31, 2017 · 4 comments
Labels
Milestone

Comments

@guettomusick
Copy link

guettomusick commented Oct 31, 2017

When opening visual studio code on a Mac OS High Sierra, autoindexing for intellisense takes palce, and it doesn't include the include path for the std library of C++ under esp8266 platform.

If I manually include this include paths,

"~/.platformio/packages/toolchain-xtensa/xtensa-lx106-elf/include/c++/4.8.2"
"~/.platformio/packages/toolchain-xtensa/xtensa-lx106-elf/include/c++/4.8.2/xtensa-lx106-elf"

the problem is solved, but when I restart visual studio code, the indexing takes place and those include paths are missing again.

@ivankravets ivankravets added the bug label Nov 1, 2017
@ivankravets ivankravets added this to the 3.5.0 milestone Nov 1, 2017
@ivankravets
Copy link
Member

Thanks a lot for the report!

Please open PIO IDE Terminal and run

pio upgrade

Restart IDE.

@guettomusick
Copy link
Author

guettomusick commented Nov 1, 2017 via email

@ivankravets
Copy link
Member

I think you can configure that in VSCode. Click on "CPP" in the bottom right corner.

@guettomusick
Copy link
Author

guettomusick commented Nov 1, 2017 via email

ivankravets added a commit that referenced this issue Dec 28, 2017
… issue #1236, issue #1235, issue #953, issue #1118, issue #1107, issue #1196, issue #1179, issue #1161, issue #1126, issue #104, issue #1033, issue #1034, issue #1175, issue #1173, issue #1155, issue #1188, issue #1111, issue #1153, issue #1150, issue #1145, issue #1139, issue #1137, issue #1170, issue #1157, issue #1102, issue #1105, issue #1140, issue #1154, issue #1066, issue #1038, issue #1054, issue #1055, issue #1061, issue #1017)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants