Re: [cdt-patch] Patch for Approval: Standard make info in cdtproject fil

[Sean Evoy <sevoy@xxxxxxxxxx>]

Thanks Alex,
It's always good to base decisions on customer feedback. I honestly have 
not given this as much design thought as I should. First blush is that it 
must be possible for lead build engineer to set the data for all team 
members. That gets checked in and out of the CM system. If the individual 
overrides the settings, maybe we use the project properties to store the 
information for that user. Really, though, it is up to the individual 
build system to reconcile the two, so we are probably lurching towards the 
right way of doing things. We really need to take a deep breath after 1.2 
and rationalize all of this.

> >
> > Yes, that is correct. The old standard build project settings are
> > persisted in the project metadata via the properties mechanism, just 
as
> > they were before. This was done intentionally to minimize the impact 
of
> > the changes I was making to add include and symbol information to the
> > standard make. I did not want to use properties because I believe that 
in
> > a larger project, this data may have to be shared between team 
members.
> >
> 
> One of our big customer strongly insists on sharing all build options
> between project members. But it doesn't mean that all other customers 
would
> be happy of that. For example I personally don't like to share settings 
for
> debug/release or code profiling options with my co-wokers - it just 
doesn't
> make sence in my oppinion. That's why we decided to create one more 
control
> in preferences (one more! :-)) to switch between local and global 
property
> storage. Of course it impacts only the group of reasonably selected
> properties such as listed before or for example temporarely
> activate/deactivate targets for multi-target project.
> 
> Alex Chapiro
> 


Sean Evoy
Rational Software - IBM Software Group
Ottawa, Ontario, Canada