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

[kesselhaus@xxxxxxx]

Is the C-language extension out of this scope?
I mean, if compiler understand some Non-ANSI-C extensions, like __at(...)
and the like, though, Parser and Indexer don't yell on such statements,
because one toolchain supports this and the other something else.

> Here are the MBS proposed tasks in the requested format. The bugzilla
> entry number will change as we complete individual designs.
> 
> 
> 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.
> Bugzilla entries: 81450
> Priority: High
> Status: In design
> Milestone: TBD
> 
> - 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.
> Bugzilla entries: 81450
> Priority: High
> Status: In design
> Milestone: TBD
> 
> - 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.
> Bugzilla entries: 81450
> Priority: High
> Status: In design
> Milestone: TBD
> 
> - 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.
> Bugzilla entries: 81450
> Priority: High
> Status: In design
> Milestone: TBD
> 
> - 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.
> Bugzilla entries: 81450
> Priority: High
> Status: In design
> Milestone: TBD
> 
> - 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.
> Bugzilla entries: 81450
> Priority: High
> Status: In design
> Milestone: TBD
> 
> - 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.
> Bugzilla entries: 81450
> Priority: High
> Status: In design
> Milestone: TBD
> 
> - Integrate into Scanner configuration discovery mechanisms:
> Update MBS to use the new CDT mechanisms.
> Bugzilla entries: 81450
> Priority: High
> Status: Not started 
> Milestone: TBD
> 
> - Tool Input ordering
> Allow the user to specify the order for input files for tools that
> accept multiple files (e.g. Linker).
> Bugzilla entries: 81450
> Priority: Medium
> Status: Not started
> Milestone: TBD
> 
> - 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.
> Bugzilla entries: 81450
> Priority: Medium
> Status: Not started
> Milestone: TBD
> 
> - Support new Remote Building
> Allow tool integrators to use the new Remote System support in CDT 3.0.
> Bugzilla entries: 81450
> Priority: Medium
> Status: Not started
> Milestone: TBD
> 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
> 

-- 
Lassen Sie Ihren Gedanken freien Lauf... z.B. per FreeSMS
GMX bietet bis zu 100 FreeSMS/Monat: http://www.gmx.net/de/go/mail