Handle large c projects with Indexer [message #1756491] |
Fri, 17 March 2017 15:01  |
Eclipse User |
|
|
|
Hi,
usually a developer wants to have all c and h files together in eclipse, even if he is working only on certain parts. During development c and h files are added or removed from project, but this will lead to indexing the complete project again, which takes always a lot of time (e.g. 1hour, progress 75%) . Sharing the eclipse workspace with pdom-file could be one solution, but do you see other workarounds here?
Thanks and have a great day.
|
|
|
|
|
Re: Handle large c projects with Indexer [message #1756522 is a reply to message #1756518] |
Sun, 19 March 2017 03:41  |
Eclipse User |
|
|
|
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.53966 seconds