From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Gaff, Doug
Sent: Monday, March 27, 2006 1:28
PM
To: CDT General developers list.
Subject: [cdt-dev] Notes from
Friday at Intel
Hi folks,
I took some very rough notes at
Friday’s meeting. Perhaps “TPTP Randy” and I can merge
our notes for the Wiki.
The presentations are probably the
most useful thing, though.
HTH,
Doug G
Changes for Fortran (Craig)
o Project
Creation
·
Desire is to have a project be a "compiled-language
project" and not be specific to a language.
·
To Do 3.1
§
Perspective / wizard branding for ISV's?
·
To Do 4.0
§
How does user tell us which languages are used?
§
Remove convert project.
o Perspective
o C/C++ Projects
View
o Outline
o Launch
o Preferences
General Discussion - 4.0 (Doug S)
o Callisto
benefits - you get more code in, possibilities:
·
Static Analysis features with TPTP
·
Modeling with GMF?
o Doug would like
to move CDT to yearly release and align with Eclipse train, of course
o Momentum is
growing - more contributors coming
o Multi-language
o Flexible Hierarchy
for Debug
o Potential major
release with API lock-down
o Flexible
resources - does RSE use this?
New Project Model (presentation by
Leo)
o MBS will go
into maintenance. New development connected with Project Model.
o Mikhail S -
leading the effort in 4.0. Leo T has to move on to another project.
o Goals
·
Increase usability: make common tasks simple, apply
some MBS concepts CDT-wide.
·
Increase tool-integrator support: user supplied information
CDT-wide
·
Multiple programming language support
o Why?
·
Usability: project creation flow needs to be
redesigned. Lack of "it just works."
·
All of CDT isn't working from the same information.
·
Tool chain defaults. Toolchain integrator should
provide the installation and project static information (command name, options,
etc) so the user doesn't have to.
·
Increase customizability: multi-language, build
targets, build settings
·
Increase extensibility
·
Increase support for tool providers
§
External SDK's. e.g. C++ class library inclusion in a
build
§
Deployment steps
o User visible
·
Make concept of "build configuration" a
pervasive part of CDT
§
All builders will support configurations
§
Each build configuration will be associated with 1
toolchain (0 allowed for Standard Make)
§
Each configuration can use a different toolchain
·
Tool selections (editor, builders, views, properties,
preferences) based on Eclipse content-types
o New Model
Schema
·
Used by tool integrators to describe their tool
definitions to CDT
·
Saved in CDT project files
·
Tool-integrator definitions can be provided by
§
CDT extension point
§
Dynamically by implementing an interface
§
XML files in a pre-defined location
o TBD parts of
the model
·
Multiple build targets
·
External SDK's
·
Deployment
·
Per-folder settings
o Why not?
·
API breakage, UI changes
Project Model and Core API Changes
(presentation by Mikhail Sennikovsky)
o (see
presentation)
o Debugger,
Debug, Launch, Source Information - will be integrated with the toolchain
information.
·
Is this a deviation from the platform?
·
Perhaps Darin is doing something here, though?
PDOM, Parser, Indexer (Doug S -
demo)
o C/C++ Index view
- navigator that performs a similar function to our Symbol Browser.
o Michael had
several questions about database issues.
o Doug S - showed
code
MBS Build Model and Internal
Builder (Mikhail S presentation)
o (see
presentation)
o BuildStep - a
tool invocation: input and output resources
o BuildResource -
a build resource: path, build steps
o BuildDescription
- root element for accessing the build step/resource hierarchy
o BuildDescriptionManager
- entry-point for build model operations
o Internal
builder UI will be in 3.1 only as experimental
Project Creation UI Discussion
o 3.1:
Language - Builder (Managed vs. Standard) - Project Name - MBS - Advanced
o 4.0
·
Multiple-language support
·
Project templates
·
Additional Builders (beyond standard and managed)
·
Better usability
·
More flexibility in changing builders, toolchains, etc.
after project creation
·
More flexibility for tool-integrators to use
"reference" parts of the project creation UI and logic.
o Continue to use
wizard? Suggestion to use tabs instead with a summary page.
o Most common
selections: language, project template, toolchain, builder
Template Engine proposal update
– Neil Taylor
o Symbian uses
this to create projects.
o This is going
to be contributed to the CDT project.
o Symbian will
have a committer in CDT to support this.
o Demo of project
template engine from Symbian Carbide product.
HP C/C++ Remote Dev Plug-in 1.0
for Eclipse - Sumit Sarkar, Alex ?
o (presentation)
o www.hp.com/go/eclipse-remotedevplugin
o Will be
contributing this back to CDT.
o What about RSE
and the CDT remote launch? They are aware of RSE. Potential
architectural issue given competition directly with RSE.
Mixed mode debugger, JDT/CDT
projects - Vitaly Provodin - Intel
o (presentation)
o Eclipse +
Harmony project to explore possible solution
o Short term
plans: Develop an XDI-based debugger plug-in and get working with XDI JVM
agent.
o Long term plans:
Create better integration with JDT and CDT components and launchers.
Create cooperative infrastructure for debuggers. Support entire
development process for mixed applications.