Eclipse Community Forums: C / C++ IDE (CDT) » "file not indexed because it was not built" errors

Home » Language IDEs » C / C++ IDE (CDT) » "file not indexed because it was not built" errors

"file not indexed because it was not built" errors [message #148756]

Wed, 13 July 2005 19:21

Eclipse User

Originally posted by: yug3sh.yahoo.com

I seem to be getting this error for all the header files (*.h) in my
project. What does this mean, and how do I get rid of it?

Thanks.

Re: "file not indexed because it was not built" errors [message #148983 is a reply to message #148756]

Fri, 15 July 2005 21:03

Eclipse User

Originally posted by: plankton.softwitch.net

Older version of cdt contains that problems. Try it with newer. Newer
version of cdt can indexing without building.

If you want to keep version of cdt, you have to make makefile manually,
or main function have to includes target header files in any path.

Yug3sh wrote:
> I seem to be getting this error for all the header files (*.h) in my
> project. What does this mean, and how do I get rid of it?
>
> Thanks.
>
>

Re: "file not indexed because it was not built" errors [message #149067 is a reply to message #148983]

Sat, 16 July 2005 23:45

Eclipse User

Originally posted by: yug3sh.yahoo.com

I'm using the latest version of CDT (3.0 RC2).

My project is a standard make project, however I'm not using makefiles
(using jam).

Is there something I can do to get rid of the errors?

Thanks.

"jiyul" <plankton@softwitch.net> wrote in message
news:db9md6$kuo$1@news.eclipse.org...
> Older version of cdt contains that problems. Try it with newer. Newer
> version of cdt can indexing without building.
>
> If you want to keep version of cdt, you have to make makefile manually,
> or main function have to includes target header files in any path.
>
> Yug3sh wrote:
>> I seem to be getting this error for all the header files (*.h) in my
>> project. What does this mean, and how do I get rid of it?
>>
>> Thanks.
>>
>>

Re: "file not indexed because it was not built" errors [message #149514 is a reply to message #149067]

Mon, 18 July 2005 11:01

Eclipse User

Yug3sh wrote:
> I'm using the latest version of CDT (3.0 RC2).
>
> My project is a standard make project, however I'm not using makefiles
> (using jam).
>
> Is there something I can do to get rid of the errors?
>

Select the errors and right-click. There's an option to delete "C/C++
Markers" or something like that.

Re: "file not indexed because it was not built" errors [message #149518 is a reply to message #149514]

Mon, 18 July 2005 13:54

Eclipse User

Originally posted by: chuck_tuffli.sierralogic.com

Patrick Turley wrote:
> Yug3sh wrote:
>
>> I'm using the latest version of CDT (3.0 RC2).
>>
>> My project is a standard make project, however I'm not using makefiles
>> (using jam).
>>
>> Is there something I can do to get rid of the errors?
>>
>
> Select the errors and right-click. There's an option to delete "C/C++
> Markers" or something like that.

This sucessfully hides the errors, but is there a way to make the
indexing sucessful?

I too have the same problem as the original poster running Eclipse 3.1
with CDT 3.0RC2 on WinXPSP2.

Re: "file not indexed because it was not built" errors [message #149521 is a reply to message #149518]

Mon, 18 July 2005 17:07

Eclipse User

Chuck Tuffli wrote:
> Patrick Turley wrote:
>
>> Yug3sh wrote:
>>
>>> I'm using the latest version of CDT (3.0 RC2).
>>>
>>> My project is a standard make project, however I'm not using
>>> makefiles (using jam).
>>>
>>> Is there something I can do to get rid of the errors?
>>>
>>
>> Select the errors and right-click. There's an option to delete "C/C++
>> Markers" or something like that.
>
>
> This sucessfully hides the errors, but is there a way to make the
> indexing sucessful?
>
> I too have the same problem as the original poster running Eclipse 3.1
> with CDT 3.0RC2 on WinXPSP2.

Oh - sorry - I don't know how to make it stop generating the errors. I
have the same problem. It's not too bad, though, so I'm just ignoring it
and hoping it gets better in a later release.

Re: "file not indexed because it was not built" errors [message #150040 is a reply to message #148756]

Tue, 26 July 2005 11:01

Eclipse User

It means that you're using the Full C/C++ Indexer and that you have no build
information. (i.e. no include paths are set up, so there is no way for the
parser to know where to look). You can either enter these paths yourself or
Rebuild project to get some defaults set.

"Yug3sh" <yug3sh@yahoo.com> wrote in message
news:db47ll$ma8$1@news.eclipse.org...
> I seem to be getting this error for all the header files (*.h) in my
> project. What does this mean, and how do I get rid of it?
>
> Thanks.
>
>

Previous Topic:	unable to call routines from another module
Next Topic:	Relative Path to Absolute path problem

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jun 22 06:53:54 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter