RE: [cdt-dev] MBS Plan items for CDT 3.0 (proposed)

["Recoskie, Chris" <crecoskie@xxxxxx>]

I think separate Bugzilla entries probably makes more sense otherwise
managing the design and all of the input from the community will be
unwieldy.

We're going to review the proposal in detail internally on Friday so I
should be able to give some more feedback early next week.

___________________________________________
 
Chris Recoskie
Software Designer
IDE Frameworks Group
Texas Instruments, Toronto
 
 

> -----Original Message-----
> From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
> Behalf Of Treggiari, Leo
> Sent: Wednesday, February 09, 2005 11:47 AM
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] MBS Plan items for CDT 3.0 (proposed)
> 
> 
> This is a summary description of the MBS proposed work for CDT 3.0.
> Further details with an initial description and some design can be
found
> in Bugzilla #81450.  We are currently working on more complete
> descriptions and designs.
> 
> Question:  Would it be better to post each complete design as a
separate
> bugzilla, as opposed to a single document with all of the designs?
> 
> Regards,
> Leo
> 
>
========================================================================
> =
> 
> Managed Build System
> 
> - Multi-Version Tool-chain support
> Add the ability to support multiple versions simultaneously and to
> support migration from one version to another.
> 
> - Converter extension point
> Add the ability to convert Projects, Tool-chains, Tools, Builders.
This
> supports tool version migration (previous item) and converting a
project
> from one tool-chain to a different one.
> 
> - Tool-chain installation support
> Add an isSupported extension callback that allows a tool-chain
> integration to report whether the tool-chain that is deswcribes is
> installed on the system.
> Add an initialize extension callback that allows a tool-chain to
> initialize itself.
> 
> - Build macros - ${macro}
> Add support for build macros in configuration properties that accept
> text.  MBS will define many built-in macros (files, paths, names).
> Tool-chains can define additional macros and values at configuration
and
> project scope.  Users can define additional macros and values at
> configuration, project, and workspace scope.  Macro values can be
> context sensitive (e.g. have a different value depending upon the
> current file, configuration, project, etc.).  More specific scope
> overrides less specific (e.g. configuration takes precedence over
> workspace). User defined values override tool-chain defined values
which
> override built-in values at the same scope.
> 
> - Environment variables
> Allow tool-chains to define additional environment variables and
values
> at configuration and project scope.  This includes being able to set
the
> executable, include and library paths, so that the user is not
required
> to set the environment before starting Eclipse.  Users can define
> additional variables and values at configuration, project, and
workspace
> scope.  More specific scope overrides less specific (e.g.
configuration
> takes precedence over workspace).  User defined values override
> tool-chain defined values which override built-in values at the same
> scope.  Environment variables are passed to the build process and can
be
> used as build macros.
> 
> - Custom build steps (command line scripts)
> Add support for Pre & Post build command scripts.  Allow a user to
> define a set of commands to be run on all files with a specified
> extension(s).  This is a simple tool integration method that could be
> used with tools such as lex and yacc.  Allow a user to define a set of
> commands to be used to build a specific source file.
> 
> - Custom file extensions
> Allow the user to modify the default file extensions that map to a
tool.
> CDT already has the C/C++ File Types property page.  MBS will use that
> information.  MBS would also like to extend that page to allow
> tool-integrators to define "file-types" and default extensions for any
> tool that they want to integrate into their tool chain - for example,
> lex, yacc, or a Fortran compiler.
> 
> - Tool Input ordering
> Allow the user to specify the order for input files for tools that
> accept multiple files (e.g. Linker).
> 
> - Option enhancements:
> Add an extension callback for option "applicability".  This would
allow
> a tool-chain to specify whether or not an option is currently
displayed,
> enabled, and used in command-line generation.
> Support the browseType attribute for String properties by displaying a
> file selection dialog box.
> 
> - Integrate into Scanner configuration discovery mechanisms:
> Update MBS to use the new CDT mechanisms.
> 
> - Support new Remote Building
> Allow tool integrators to use the new Remote System support in CDT
3.0.
> 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev