Closed joelvonrotz closed 5 years ago
Previously, the intelliSenseEngineFallback was set to Default instead of Disabled, so if a header was missing it would not show any squiggles. The completion comments are probably coming from the tag parser. Can you go to the definition of CAN and see why IntelliSense isn't compiling the definition? I would guess a define is not set. Also, it seems like you may want to set the intelliSenseMode to gcc-x64, unless you're compiling with cl.exe.
Previously, the intelliSenseEngineFallback was set to Default instead of Disabled, so if a header was missing it would not show any squiggles. The completion comments are probably coming from the tag parser. Can you go to the definition of CAN and see why IntelliSense isn't compiling the definition? I would guess a define is not set. Also, it seems like you may want to set the intelliSenseMode to gcc-x64, unless you're compiling with cl.exe.
Hi Sean I was able to fix it. The whole mbed library is huge and it seems that adding one include path to a completely different compiler fixed the problem for now.
So it's my bad.
Type: LanguageService
Describe the bug
Classes and various other definitions have the "identifier XYZ is undefined"-error in the normal Intellisense-mode, despite still being content-aware and findable with "Go to Defintion". Tag-Parser works without any problems. A couple of versions ago (I don't know which one it was) the Intellisense seemed to work, the only errors that occured where missing files.
The code is compile-able with Keil uVision 5 and the defines from uVision have been included in the C/C++ Properties.
To Reproduce
Content of c_cpp_properties.json
Expected behavior The code is content aware without any errors.
Screenshots Image shows a CAN-object called "can". The CAN-class gives of the Undefined-error, while calling functions from the object "can" is correctly content-aware (the functions are CAN-functions only).
Modified settings