|
Re: Handle large c projects with Indexer [message #1756505 is a reply to message #1756491] |
Sat, 18 March 2017 04:24 |
David Vavra Messages: 1426 Registered: October 2012 |
Senior Member |
|
|
Not sure what you mean by 'large'.
One of my biggest (dlib c++ library) has 758 header files and 628 c/c++ files.
Takes around 3 min to completely index.
You might try it yourself by temporarily downloading and indexing
https://sourceforge.net/projects/dclib/
If it takes longer than 5-10 min then something is definitely wrong.
Perhaps you've got some files that are difficult for the Indexer.
Adding or deleting files should normally update the index without a rebuild.
You may want to consider breaking up the code into one or more libraries each in a separate project.
You could try modifying the Indexer options.
I'm thinking the Indexing strategy and Cache limits
I believe these are the defaults;
HTH
[Updated on: Sat, 18 March 2017 04:33] Report message to a moderator
|
|
|
|
Re: Handle large c projects with Indexer [message #1756522 is a reply to message #1756518] |
Sun, 19 March 2017 07:41 |
David Vavra Messages: 1426 Registered: October 2012 |
Senior Member |
|
|
None that I know of.
Note that makefile generation and indexing are different things.
A Makefile project simply means you (vs. CDT) will build the makefile.
It has nothing to do with indexing per se.
The indexer really only needs the compiler to discover its builtin paths and macros.
You could put them into Eclipse by hand instead.
Without having your code it's difficult to make any recommendations.
A few in general,:
Make your projects as small as possible by separating the code into logical entities using symbolic inks to shared code.
When possible, make libraries of common code and have separate projects for each library.
When cross-compiling avoid networking as much as possible.
Look at how GCC implements its libraries which essentially uses multiple switches (via preprocessor defines) to implement various compile configurations.
|
|
|
Powered by
FUDForum. Page generated in 0.02901 seconds