Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] CDT 2.1 RC1 Now Available for Testing 
Here is a What's New section for Managed Build System:

Managed Build System (MBS):

* MBS uses a new model for defining tool-chain integrations.  Refer to
the
  Managed Build System Extensibility document for details.  It can be
found
  in the CDT on-line help at Concepts -> Build -> Managed Build 
  Extensibility Document.
    * Old model definitions continue to be supported.
    * The new model should be used in the future since not all new 
      functionality will be available from the old model.  In general,
no 
      significant effort will be expended in making new functionality
work
      with the old model manifest files.  However, in some cases, new
      functionality will automatically work with old model manifest
files.
      The new functionality in this release appears to work with old
model 
      manifest files.  The GNU tool-chain definition has been updated to
use
      the new model.
    * Old model project (.cdtbuild) files are converted upon approval
      by the end-user.  Converted project files will no longer work with

      CDT 2.0.
 
* MBS now supports file-specific tool command line options:
    * A specific file in a configuration can use different tool options
      than the rest of the files in the configuration.
    * A specific file can be excluded from the build of a configuration.

* There are new attributes that add flexibility to tool command line  
  Generation.  Details can be found in the Managed Build System 
  Extensibility document.
    * Tool.commandLinePattern:  Specifies a command "pattern" that
indicates 
      how the parts of the command line are used to create the entire
      command line.
    * Tool.commandLineGenerator:  The name of a class that implements 
      IManagedCommandLineGenerator.  This interface allows complete
control
      Over the command line.
    * Option.command:  The command provides a "pattern" for specifying
where 
      the value should be placed for options of type string and
stringlist.
      The pattern can contain the replaceable variable VALUE.  If no 
      ${VALUE} is specified in the command, the option value is appended
to 
      the end of the specified command (as happens in CDT 2.0).

  Modified UI:
    * Error parsers are no longer selectable in the project creation
wizard.
      This is because error parsers are set per-configuration, and 
      per-configuration changes are made via the property page.
    * C/C++ Build page of MBS project properties now contains all of the
      per-configuration settings for the project.  There are 4 tabs for 
      Tool Settings, Build Settings, Error Parsers, and Binary Parsers.
      Note that binary parsers are not yet applied per configuration
because
      the rest of CDT is not currently set up to handle it.
    * File properties now contains a C/C++ Build page where the tool
options 
      for a particular file can be set.


Regards,
Leo


-----Original Message-----
From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
Behalf Of Dave Inglis
Sent: Tuesday, November 09, 2004 1:40 PM
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] CDT 2.1 RC1 Now Available for Testing

Here is a Whats New I have started for 2.1 feel free to add anything 
missing.

What's New

Core
* Support for 64 bit binaries (binary parser and debugger)
	
UI
* New Class wizard
* New C/C++ wizards toolbar shortcuts (New Source file/Header

file/Source folder/Class).
* C/C++ Outline view supports grouping and filtering
* C/C++ editor code folding
* Makefile editor structured folding
* New Makefile editor preferences
* Code formatting framework.
* New help contribution framework, to support hover help and help book
   linking from within the C/C++ editor.

Debug
* Thread breakpoints.
* Support 64 bit debugging

Launch
* Debug variable support in environment, argument and working directory.
* Changes to support new debugger interface.


Douglas Schaefer wrote:
> CDT 2.1 RC1 is now available for testing. Please raise any bugs you
find 
> in bugzilla.
> 
> The build is available at: 
> http://download.eclipse.org/tools/cdt/builds/2.1.0/RC1
> 
> Current bugs: 163
> 
> *** Change Report ***
> 
> Contributors, please feel free to correct/elaborate/expand. This
report 
> was created by going through the results of the Compare with version 
> command (to CDT_2_1_RC0).
> 
> Files changed since RC0: 169 (not including test plugins)
> 
> Core
> - Bug fixes in type cache, indexer, parser
> - Changes to framework for code formatter
> - Updates to makefiles for win32 libraries
> 
> UI
> - Bug fixes in class browser, content assist, help provider, new class
& 
> file wizards
> - Changes to code formatter including new preference page
> - Updates to new class wizard (more like a feature deferral)
> 
> Build
> - Fixes for 1.2.1 import
> - Numerous fixes for managed build
> 
> Debug
> - Fixes for variable management
> - New functionality to capture return value of function
> - Refactoring of Configuration into Session and Target Configurations
> - Move refresh and auto-refresh actions for shared libs and registers
from 
> core to MI
> - Removed signal manager interface, update manager
> - New implementation for expressions for large arrays
> - Added support for MI's -interpreter-exec
> - Added support for fresh preferences in MI
> 
> Doug Schaefer, IBM's Technical Lead, Eclipse CDT
> Ottawa Lab, IBM Canada, Rational Software Division
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev

Back to the top