|RE: [cdt-dev] How to determine when the project indexing is compl eted|
I agree with your suggestion of not waiting for the Index while building.
The only case when I have a trouble with incomplete index now is my Internal Builder/Build Model dependency calculation JUnits. I had to put a delay in those tests to ensure that the index is completed before the Build Model is generated, but in case there is an API to get the Index status I’d switch to use it instead.
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
There’s no such mechanism in place today. It should be possible to generate an event when the indexer job queue becomes empty and the indexer job finishes. However I don’t think we want to hold up building until the indexer is finished. We’ve done that in the past and it really sucked.
For build dependencies, all you really need is the dependencies at the time of the last build. If dependencies change, the files change and rebuild anyway. With the new Fast indexer which has super fast incremental indexing times, you should have no problem keeping up. The only time you need to worry is when the initial index is created for new/imported projects, in which case you should be doing a full build anyway.
I’d be interested in hearing about cases where this wouldn’t work.
Back to the top