Indexing strategy configuration [message #236119] |
Sun, 19 July 2009 08:11  |
Eclipse User |
|
|
|
Hi,
Under Window->Preferences->C/C++->Indexer there is an "Indexing strategy"
which has 2 options selected by default:
1) Automatically update the index
2) Update index immediately after every file change.
I don't understand the exact meaning of these options. For example if
option 1) is selected and option 2 is not. I change some cpp file and
press save. When will the index be updated? Is there any documentation on
this?
Thanks,
Yevgeny
|
|
|
|
|
Re: Indexing strategy configuration [message #479926 is a reply to message #478744] |
Thu, 13 August 2009 03:45   |
Eclipse User |
|
|
|
Jonah Graham wrote:
> Hi Yevgeny,
>> 1) Automatically update the index
> This option control whether the indexer will update itself automatically
> in the background, or whether you need to manually tell the indexer to
> refresh based on changes. To manually update index, right click on a
> C/C++ Project, choose Index->Update with Modified Files.
>> 2) Update index immediately after every file change.
> This controls whether the index is updated every time a file is changed,
> or only when the project is built. In this case if you have Build
> Automatically turned on the effective behavior ends up being basically
> the same.
Currently I unchecked this option on workspace level, my project uses
workspace configuration. "Build Automatically" is unchecked.
Use case: Some files were changed in file system, I refreshed the project
using project explorer. Immediately indexing was ran, I would expect
indexing to run after build project is done. Also every time I change some
file indexing is updated. First option (automatically update the index) is
checked (selected).
Is this a bug?
> I hope that helps,
> Jonah
|
|
|
|
Re: Indexing strategy configuration [message #1086444 is a reply to message #1076774] |
Wed, 14 August 2013 04:01  |
Eclipse User |
|
|
|
Hi,
I am not familiar with this decoration feature. Since JUNO issues I am still using Indigo, starting evaluating Kepler just few days ago.
Regarding your question, why some files are not being indexed or decoration not working. The question is whether code navigation (call hierarchy, type hierarchy, etc.) work? Also what would happen if you generate parser log on this file? How many unresolved headers do you have in your project? What is the indexer statistics (could be found in error log view after full index rebuild)?
I am not sure if the problem is with indexing or with decoration feature.
If we assume that the problem is with indexer, I would suggest opening a bug on this issue. It will be great if you could post a file or code example for reproducing this issue. Also you can try asking guys from CDT mailing list.
Thanks,
Yevgeny
|
|
|
Powered by
FUDForum. Page generated in 0.09583 seconds