Eclipse cannot find <stdint.h> & <string.h> on Mac OS X

[Bee]

Hello everyone~

I'm setting up an eclipse and gcc development environment on Mac OS X following Vidar Berg's tutorial here:https://devzone.nordicsemi.com/tutorials/7/development-with-gcc-and-eclipse/

However, I met two problems.

1.According to the Import existing Eclipse project to workspace, I cannot import any of the example of the attachments. When I go to the folder of the makefile, nothing can be imported.

2.When I try to Create a new Eclipse project, according to the Enable auto discovery of symbols, include paths and compiler settings, eclipse solved some problem but still cannot find <stdint.h> & <string.h>, and no Key symbols appear. I can't find the reason.

Is there anybody know why?

[Håkon Alseth]

Hi,

Q1: Did you download the "template project" for blinky located in the end of the tutorial and point to it? If you point directly to the standard SDK, it will not have anything else than a makefile, and eclipse will state it's empty.

Q2: These are standard includes, which shall be provided by the compiler. It's the eclipse c/c++ indexer that triggers, as this is not a path that is included in the Makefile.

You can add the path to stdint/string etc by adding a include in the c/c++ indexer: www.eclipse.org/.../article4.php

These are in the include folder to the compiler. I'm not sure where its located on osx by default, but on windows it's located here:

C:\Program Files (x86)\GNU Tools ARM Embedded\5.2 2015q4\arm-none-eabi\include

Cheers, Håkon

[Vidar Berg]

Paths to the standard libraries should be added automatically if you enable CDT Built-in Compiler Settings Cross ARM as described in the "Enable auto discovery of symbols, include paths and compiler settings" of the tutorial.

[Bee]

Sorry, I have to tell you it won't work. I have to Macs, a Mac mini and a Macbook Pro. Both of them met this problem and I'm sure I just followed that tutorial. Are there any other potential reasons?

[Vidar Berg]

hm, please make sure you have set the correct path to your toolchain in preferences -> C/C++ -> Build -> Global tool paths. On my windows system it is C:\Program Files (x86)\GNU Tools ARM Embedded\4.9 2015q3\bin

[Bee]

I set Eclipse global preferences like this: Build tool folder: /usr/bin/make Toolchain folder:/usr/local/gcc-arm-none-eabi-4_9-2015q3/bin I'm not sure if it's right because this is a mac os x path. But I'm sure both the examples you gave in the tutorial works fine, no problem.