Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Major PDOM changes in HEAD

Yes. The unfortunate answer is that this has always been true with CDT's
indexing. There is a proposal on the table, however for the concept of build
configurations to spread throughout the CDT instead of currently being just
a managed build concept. There will still be a lot of work, however to
figuring out how that will manifest itself in features such as Open
Declaration (which config? all configs?)

Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, Tools PMC member

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Matthias Spycher
Sent: Friday, May 19, 2006 12:31 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Major PDOM changes in HEAD

Doesn't that problem also exist in a single project with multiple build 

Lothar Werzinger wrote:
> On Friday 19 May 2006 07:09, Doug Schaefer wrote:
>> Hmm, now that I've met my performance targets using caching, maybe I'll
>> it back to PDOM per project. The other problem I ran into was the amount
>> of memory mapped chunks allowed under Windows which I addressed by making
>> the chunks bigger.
>> I have to agree that this would make the reuse feature easier. I'll sleep
>> on it but if you have a strong opinion let me know. The good news is that
>> it should be easy to change back (and is a good test of my architecture
> I think a per workspace solution is doomed sooner or later. What for
> happens if you have two projects in the same workspace that contain the
> files, but need to be built with different set of macros (like local cross

> builds)?
>> Doug Schaefer, QNX Software Systems
>> Eclipse CDT Project Lead, Tools PMC member
> Lothar

cdt-dev mailing list

Back to the top