Re: [cdt-dev] (Dynamic) project references causing unnecessary rebuilds

["dmsubs" <dmsubs@xxxxxxxxxxxxx>]

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On Behalf Of James Blackburn
> Sent: 03 February 2011 15:37
> To: CDT General developers list.
> Subject: Re: [cdt-dev] (Dynamic) project references causing unnecessary
> rebuilds
> 
> On 3 February 2011 14:54, dmsubs <dmsubs@xxxxxxxxxxxxx> wrote:
> > James,
> >
> > It is not too much building that I am worried about. What I am worried
> > about is that it is unnecessarily rebuilding all of the source files.
> > I can live with an invocation of make that does nothing, but not one
> > that decides it has to rebuild, when in fact it doesn't.
> 
> Ok.  The main reason it happens is because only one confiugration is
active at
> any one time.  So if your project references a non-active configuration,
CDT
> makes pretty pessimistic assumptions about which files have changed since
> the configuration was last built (as it's not built by default).  Hence
when
> running the config build it rebuilds all the source.  References between
active
> configurations _shouldn't_ rebuild all the time.

But it is... I use the "Active" build configuration in the reference.

> 
> All of this is in the process of being fixed.  The platform now knows
about
> build configurations, so we keep a delta per configuration.
Understood, but I am trying to understand the limitations of the current
implementation. It seems my completely trivial example doesn't work, which
means it is completely useless.

> 
> Cheers,
> James
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev