Eclipse Community Forums: C / C++ IDE (CDT) » Ignored include paths when using manual makefile

Home » Language IDEs » C / C++ IDE (CDT) » Ignored include paths when using manual makefile(Eclispe Kepler - CDT project - manually provided makefile and include paths. Compilation is all right but content assist isn't.)

Show: Today's Messages :: Show Polls :: Message Navigator

Ignored include paths when using manual makefile [message #1403807]

Sun, 27 July 2014 21:08

Anthony rainbow-eagle

Messages: 1
Registered: July 2014

Junior Member

Hello,

I am developping a software using a peculiar toolchain (kallistiOS for dreamcast) in a peculiar environment (Cygwin32).
Everything is perfectly functional and I get to successfully compile code using a terminal and makefiles.

By now, I would like to set up Eclipse Kepler's content assist (code highlighting, code completion etc.) in order to facilitate the development.

I created a CDT project that uses a manually provided makefile and I manage to compile the code as needed, just like it was done before the use of Eclipse.

Nevertheless, Eclipse does not "assist" the development at all since it has no idea about the very specific header files I include (those are marked "unresolved inclusion").

Hence, I manually added several include directories to my project properties (Properties > C/C++ General > Paths and Symbols > "Includes" tab)
(I also added some library paths in a similar way)

Those include and library paths added, nothing seems to have changed (the "unresolved inclusion" mark is still present and the Project Explorer view does not display the include path I added).

I do not understand how to have Eclipse considering those include paths and therefore kindly request assistance.

Attachment: includePaths.jpg
(Size: 313.82KB, Downloaded 182 times)

Report message to a moderator

Re: Ignored include paths when using manual makefile [message #1403903 is a reply to message #1403807]

Mon, 28 July 2014 14:10

Doug Schaefer

Messages: 135
Registered: July 2009

Senior Member

I've seen some odd behaviour similar to that as I experimented with new toolchains. I'd suggest raising a bug for this. Any include path put into the Includes tab should be considered.

Report message to a moderator

Previous Topic:	"#if defined(xx)" code highlight
Next Topic:	Luna, can't open non-c files from project explorer.

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 10:33:29 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter