Re: [cdt-dev] Indexer and different build configurations

[Martin.Runge@xxxxxxxxxxxxxxxxx]

Hi Marc-Andre,

That sounds good. Looking forward to
the team shared index ... 

Thank you.
Martin



Von:      
 Marc-Andre Laperle
<malaperle@xxxxxxxxx>
An:      
 "CDT General developers
list." <cdt-dev@xxxxxxxxxxx>
Datum:      
 2015-11-02 15:24
Betreff:    
   Re: [cdt-dev]
Indexer and different build configurations
Gesendet von:    
   cdt-dev-bounces@xxxxxxxxxxx

---

Hi Martin,

There is only one index stored on disk at a time. There was good
progress done to support multiple, see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=183781.
It's in a state
of a working prototype. I think we could finish this for CDT 9.0. Your
help in testing this would be useful. I can update the branch for this
in the very short term then we can look at the remaining issues,
here's a copy/paste of what I thought was left to do a while ago:
- Handling exporting/importing team shared index. We need to update the
UI, etc.
- What to do when the settings for an inactive configuration change.
Delete that file and rebuild the index when the user changes the
active configuration?
- Clean up the obsolete index files when upgrading. The pdom files
used to be foo.12345.pdom now they are foo.Debug.12345.pdom, etc.
- Unit Tests

Cheers,
Marc-Andre

On Mon, Nov 2, 2015 at 6:06 AM,  <Martin.Runge@xxxxxxxxxxxxxxxxx>
wrote:
> Hi all,
>
> I experience some inconsistant behaviour of the indexer in the following
> scenario: I have defined two build configurations:
>
> - debug_x86
> - debug_arm
>
> They build the same project with different toolchains and therefore
include
> header files from different paths. An example::
>
> std::cerr is defined in
> #include <iostream>
>
> debug_x86  ->  /usr/include/c++/4.8/iostream
> debug_arm  ->  /path/to/cross/compiler/include/iostream
>
> I found three different settings for the CDT indexer, that influence
how
> this is handled:
>
> 1) Use the build configuration specified in the project's indexer
settings
>   This one is clear and behaves like expected.
>
> 2)   Use active build configuration
>   2a)  Allow heuristic resolution of includes
>         The Indexer asks the user, which of the
two header versions to use
>
>   2b) Do not allow heuristic resolution of includes
>        The indexer uses the correct header file
for both configurations, but
> it completely rebuilds the index after each change of the build
> configuration!
>
> Rebuilding the index every time the configuration is changed is not
feasible
> IMHO, except for very small projects.
>
> As far as I understood, the index is something tied to the configuration.
If
> I use several configurations, I get the same number of indexes. Is
there a
> way to keep them spererate and just switch between them?
>
> best regards
> Martin
>
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev