pure-gcc + Eclipse CDT autodiscovery / scanner discovery

[Jason De Lorme]

Has anyone been able to get Eclipse working with the pure-gcc makefiles and autodiscovery of include files?

I can get Eclipse to build my project using the pure-gcc makefiles, but what I cannot get to work is the scanner discovery / indexing whereby Eclipse automatically finds include files. If I specify include paths in Eclipse manually, this works, but this is not efficient as we already have the includes mapped out in the makefiles.

The may seem trivial and I know it has been dismissed in many older threads I've found in this forum, but this is a major issue for trying to maintain a large project and use Eclipse as the development tool using makefiles.

[Vidar Berg]

Hi, I think Nguyen is right that you need make a pure Eclipse project in order to enable auto indexing. I have tried, but not found a way for Eclipse to automatically import the Makefile paths yet. I agree that this would be a nice feature to have, so I would appreciate if anyone has a solution for this that they can share.

For Makefile projects my only suggestion for now is to copy&paste the Makefile paths to your Eclipse environment.

EDIT 29.04.2015

The new Eclipse tutorial here includes the steps to enables CDT to do autodiscovery with makefile managed projects. The key was to edit the makefile to print the command line arguments for the compiler.

[Jason De Lorme]

If you look at the goal of the GNU ARM Eclipse plugin: gnuarmeclipse.livius.net/.../ it proclaims the key CDT feature is "Indexing", and I agree. I have everything working just fine with Eclipse building my make files, it even automatically finds the correct GNU ARM standard definitions <stdint.h>, etc...

Maybe this is all that it will automatically do and I don't profess to understand Eclipse CDT Indexing in great detail, but my assumption would be that it could also parse my "-i" gcc commands to glean the include paths of the nrf51 SDK.