Unresolved inclusion warnings

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Unresolved inclusion warnings

Jump to solution
1,726 Views
davidsherman
Senior Contributor I

Something a little strange I'm seeing in KDS.  Seems to be an Eclipse issue, but it's not making sense.  I have multiple source files in the project.  There's a separate project in the workspace that includes several header files.  I have the top level project defined to use the includes directory I've defined, and I've used the path "${ProjDirPath}/../KELibs/Includes".  If I look under the C/C++ general properties, I see it is resolving the path properly.  Here's what doesn't makes sense.  Some of these source files in the top level project will show several warnings about unresolved inclusions, and show syntax errors as a result.  However, other source files at the same level in the project include the exact same files, and have no warnings.  Everything builds and compiles fine, I just don't understand why all these warnings are showing up for certain files.  If I look at the properties for the files with the warnings, their include paths are correct.

Labels (1)
0 Kudos
Reply
1 Solution
1,366 Views
BlackNight
NXP Employee
NXP Employee

Hi David,

Eclipse is using the 'Index' and 'Indexer' to parse all the files in the editor (in the background) and builds up a data base.

It could be that this data base is not correct any more. See Fixing the Eclipse Index | MCU on Eclipse  for how to fix it.

I hope this helps,

Erich

View solution in original post

2 Replies
1,367 Views
BlackNight
NXP Employee
NXP Employee

Hi David,

Eclipse is using the 'Index' and 'Indexer' to parse all the files in the editor (in the background) and builds up a data base.

It could be that this data base is not correct any more. See Fixing the Eclipse Index | MCU on Eclipse  for how to fix it.

I hope this helps,

Erich

1,366 Views
davidsherman
Senior Contributor I

Thank you Erich, I'll take a look at that.  I can't tell if it fixed the specific problem, because it seems to have corrected itself.  Good to know, though, thanks!

0 Kudos
Reply