Eclipse unresolved symbols only for uintX_t and some macros

[Nathan O.]

Hi,

I am working on a project running on a nRF52832, using SDK 12.3 and S130. I use Eclipse (2018-12) as my IDE.

I have followed the explanations from this tutorial : https://devzone.nordicsemi.com/tutorials/b/getting-started/posts/development-with-gcc-and-eclipse

Unfortunately, I still have some "symbols could not be resolved" issues on the interface (the program does compile fine). I only see this error for some symbols like :

• uint32_t
• APP_ERROR_CHECK
• NRF_CLOCK_LFCLKSRC
• SOFTDEVICE_HANDLER_INIT
• APP_TIMER_TICKS

All the other SDK related symbols are found perfectly. The strangest thing is that Eclipse is able to find the symbols when I do a Ctrl+click it sends me to the corresponding definition source file.

Any idea ?

[Nathan O.]

Thanks for your answer.

Here is my config below. It seems that the output parser is not working well.

[Vidar Berg]

You should have had a lot more errors if the output parser didn't work. A re-build might help.

Can you expand the "CDT GCC Built-in Compiler settings" entry in your 2nd screenshot and see if it includes your toolchain paths?  

[Nathan O.]

I have done several rebuild and refresh of the index. I has not helped.

It seems to include the toolchain path :

[Vidar Berg]

Strange, the paths appear to be correct. Are you still getting the "unresolved error" for uint32_t? Also, have you replaced makefile.common with the one I included in the tutorial? 

[Nathan O.]

Yes I'm still getting the errors, although it's only errors in the Eclipse UI. The project actually builds fine.

I have replaced the double quotes by single quotes. I have again tested with both solution (single and double) and am having the same results. I also checked with the Makefile.common included in the tutorial and it is effectively the same as the one I have where I changed to have single quotes.

[awneil]

This does seem to be a "feature" of Eclipse - I've seen it in a number of other applications of Eclipse.

(to be fair, Eclipse is not alone - Visual Studio & derivatives have similar  issues)

Perhaps Nguyen Hoan Hoang - the resident Eclipse expert & proponent - can help ... ?

[Nguyen Hoan Hoang]

Well, I am not expert of Eclipse.  Just experienced user.  This is what I found that works (for me on OSX at least).

https://stackoverflow.com/questions/11666094/eclipse-does-not-recognize-types-from-stdint-h-for-arm-windows-gcc-toolchain

[Nathan O.]

I was already using arm-none-eabi-gcc in CDT GCC builtin compiler settings. I checked and tried again : no change, I still have unresolved errors (on UI interface only) for some macros and for uint_t)

[Nguyen Hoan Hoang]

I also found this to be working. (ref stackoverflow.com/.../eclipse-c-build-error)

1. Right click on the project name
2. Then Index
3. Then Freshen All Files and wait.