[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-core-dev] CDT Indexing
|
Hi Doug,
Thanks for your reply.
Since indexed file is larger than the original file, i am fine with transfering it to local only once and referring it but what about the changes that i am doing in the remote file. How will I reflect those changes in the index file so that I shall get better search results even by considering just made changes.
Also, user does not maintain the whole copy of project. He just checks out the required files so how can we handle indexing only for those files?
Could you please suggest anything on these points?
Thanks,
Vrushali.
"Schaefer, Doug" <Doug.Schaefer@xxxxxxxxxxxxx> wrote:
This has been discussed often in the last year or so. My conjecture is that the size of the index is actually larger than the size of the source. And since the fast indexer only parses each file once, it's actually faster to keep the indexer local and access the files remotely.
But others have a different opinion.
Doug.
Hi,
CDT provides efficient indexing for local files.is there any way to achieve that indexing for remote files?
if CDT stores those indexed files somewhere and refers it to them later then how about a following approach - - having eclipse on remote server
- indexing all the files on remote server with Eclipse CDT
- copy those generated indexed files from remote server and store them locally
- refer these files in case of any search demand.
Please correct if i am going wrong some where or if there exists any better option to which
i can shift to.
Thanks,
vrushali.
_______________________________________________
cdt-core-dev mailing list
cdt-core-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-core-dev
