Re: [cdt-dev] Two more suggestions for CDT 2.0 Managed Build functionali

[Cory Bialowas <bialowas@xxxxxxxxxx>]

A question about the "beefing of
the Standard Make Plugin"...will the improved features (code complete
and hover in particular) be based on the same information if you were using
the managed make? 

The assumption that you fill in the
include paths, symbol definitions etc. and the parser populates the appropriate
content to provide these features. Or is it something separate from that
which would be used by a managed make project?

Thanks,
Cory

Cory Bialowas
Product Manager
Rational Software
IBM Software Group
Office: (613) 591 2906
Mobile: (613) 852 2073
bialowas@xxxxxxxxxx

"Alain Magloire" <alain@xxxxxxx>
Sent by: cdt-dev-admin@xxxxxxxxxxx

10/31/2003 04:41 PM

Please respond to
cdt-dev@xxxxxxxxxxx

To	cdt-dev@xxxxxxxxxxx
cc
Subject	Re: [cdt-dev] Two more suggestions for CDT 2.0 Managed Build functionality

> 
> Thanks, Leo, this is great feedback.
> 
> I am currently gathering all the info and will produce a proposal
by the 
> end of next week. We can then have a thorough discussion at the Nov
12 
> meeting and hopefully come up with some good plans to get started
on.
> 

Quick note, we are looking to "beef" up the Standard Make plugin
with all sort of things, code completion, outliner, syntax color, hovering
etc ...
Some of it is already in the Head branch.

Also for the wizard, things like dumping a generate Makefile and the interesting
possibility
of "maintaining" a Makefile for the user.  It is not a managed
builder,
it is more a smart listener that can "maintain" part of a Makefile
depending of ICElementDelta events fired by the C Core Model.
It is round trip.

Later.

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev