| RE: [cdt-dev] Custom Builders Migrating to New CDT ProjectModel[Bug115935] |
|
Hi Warren, > I understand this to
mean that the list of include paths and macros is going to be build
configuration specific, but that the index is still project-wide? Does
this mean the index has to be rebuilt every time you switch between build configs? The index should not
rebuild on every configuration change. Currently the configuration change -
reindex logic is implemented to behave similar to what we had in the Managed
Build System, i.e. in case active configuration is changed no re-index is
performed and indexer continues working with the old include path/macro
dictionary. Once include/macros settings are changed for the new Active
configuration, or for the configuration whose settings are currently used by
the indexer, the include/macro dictionary is updated to the one provided by the
currently active configuration. Mikhail From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Warren.Paul@xxxxxxxxx Hi Mikhail, I understand this to mean that the list of
include paths and macros is going to be build configuration specific, but that
the index is still project-wide? Does this mean the index has to be
rebuilt every time you switch between build configs? Thanks, Warren From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of ext Sennikovsky, Mikhail 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 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,
|