[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[cdt-core-dev] Extending includes resolving algorithm
|
Hi everybody,
We have an Eclipse plugin with our own C++ code builder. We have a specific
nature but all projects, handled by this plugin, use CDT nature as well. CDT
builder is removed. It's perfromed so that all files under the project were
indexed. From CDT point of view the project is managed build project.
Sometime CDT cann't find includes because they are not specified in include
path but defined with angle brackets <>. Our builder knows how to build them
but CDT indexer cannot resolve includes. The only way that I know is to pass
all paths with included files to CDT but this approach works really slow
(headers are indexed twice, as code in Eclipse workspace and as included
headers).
I'd like to ask if there is a way to 'help' CDT indexer to resolve includes?
I mean some programmatic way to extend CDT indexer in includes resolving
procedure.
Thanks!
--
View this message in context: http://www.nabble.com/Extending-includes-resolving-algorithm-tp23196341p23196341.html
Sent from the Eclipse CDT - core mailing list archive at Nabble.com.
