Hi
Tim,
> Q: What impacts are there for
indexing and getting configuration specific indexes rather than proejct-wide
indexes. Currently our custom builder is planning on using the "C/C++ Includes
and Macros" page to feed the indexer.
It is
currently planned that the index/PDOM information would not support the
configuration concept and would maintain the index calculated based upon some
specified configuration data. The build system integration would typically
provide include/macros information via the new
org.eclipse.cdt.core.CConfigurationDataProvider extension point that is intended
to replace the current PathEntry-related extension
mechanisms.
Mikhail
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Tim.Kelly@xxxxxxxxx
Sent: Thursday, October 12, 2006 7:47
PM
To:
cdt-dev@xxxxxxxxxxx
Subject:
[cdt-dev] Custom Builders Migrating to New CDT Project Model
[Bug115935]
Hi
- I'm looking into the design of a Custom Builder based on CDT under the current
CDT 3.1.1. After looking at some of the docs and commets on the new project
model (https://bugs.eclipse.org/bugs/show_bug.cgi?id=115935) I'm not
entirely certain the impact to Custom builders, though it's mentioned in the bug
comments but not in the documentation that I can
find.
Q:
How does the concept of making build configurations CDT centric impact a custom
(incremental) builder?
Q:
What impacts are there for indexing and getting configuration specific indexes
rather than proejct-wide indexes. Currently our custom builder is planning on
using the "C/C++ Includes and Macros" page to feed the
indexer.
Thanks,
Tim
Nokia
Developer Tools
Austin, TX