-
- Managed Builder
-
![]()
Multi-Version Tool-chain support: add the ability to
support multiple versions simultaneously and to support
migration from one version to another. Bugzilla ref. (89872)
-
![]()
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 ref. (89872)
-
![]()
Tool-chain installation support: Add an isSupported
extension callback that allows a tool-chain integration to
report whether the tool-chain that is describes is installed
on the system. Bugzilla ref. (87478)
-
![]()
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 ref. (89210)
-
![]()
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 ref.
(88497)
-
![]()
Custom build steps (command line scripts): Add
support for Pre & Post build command scripts. Bugzilla ref.
(88922)
-
![]()
Custom build steps (command line scripts): Allow a
user to define a set of commands to be used to build a
specific source file. Bugzilla ref. (88922)
-
![]()
Custom build steps (command line scripts): Allow a
user to define a set of commands to be run on all files with
a specified extension(s). Bugzilla ref. (88922)
-
![]()
Integrate into Scanner configuration discovery
mechanisms: MBS to use the new CDT mechanisms. Bugzilla
ref (81450)
-
![]()
Multiple Inputs: MBS to fully support tools that have
multiple input files and output files. Bugzilla ref. (87673)
-
![]()
New Project Wizard Enhancements: One aspect that
tool-chain developers have requested more flexibility in is
the ability to customize the new project wizard. Developers
wish to be able to add custom pages to the wizard to
facilitate such things as automatically setting launch
properties for the project, generating configuration files
for the project, and other various custom settings and
behavior. Bugzilla ref: (90334)
-
![]()
GNU Toolchain Extraction: Extract the definition for
the GNU tools so that ISVs no longer have to fork the CDT
code to remove these tool definitions which don't apply for
their products/projects. Bugzilla ref. (95110)
-
![]()
Option Enhancements: Add an extension callback for
option "applicability". This would allow a toolchain to
specify whether or not an option is currently displayed,
enabled, and used in command-line generation. Bugzilla ref:
(95762)
Support the browseType attribute for String properties by
displaying a file selection dialog box. Bugzilla ref. (63973)
-
![]()
Shared Tool Options Allow the tool integrator to
define properties that apply to the tool-chain, and not to a
specific tool. Bugzilla ref. (90481)
-
![]()
Tool Input ordering Allow the user to specify the
order for input files for tools that accept multiple files
(e.g. Linker). bugzilla ref. (87673)
|
