Skip to main content
Jump to: navigation, search


Revision as of 10:47, 28 March 2013 by (Talk | contribs) (Minutes)

CDT Summit at EclipseCon 2013

We have scheduled a one-day CDT summit at EclipseCon 2013 in Boston, MA, on Thursday the 28th of March, 2013. To help plan for this meeting, please sign up and add any agenda items you'd like to see discussed.

EclipseCon information is here:

Open to all, even if you didn't sign up :).

Time: 10:00 a.m. to 3:30 p.m.
Room: Beacon Hill 2 & 3

Attendees and Interests

  1. Marc Khouzam - Ericsson
    • Debug, Multicore, Visualizer
  2. Martin Oberhuber - WindRiver
    • Quality, Debug (TCF), Usability, Remote Edit-compile-debug
  3. Sergey Prigogin - Google
    • Refactoring, C++11 features, Codan
  4. Glen Anderson - Analog Devices
    • Debug, Usability, Multicore
  5. Dominique Toupin - Ericsson
  6. Josh Kruck
    • Debug (DSF, MS), Refactoring
  7. Bill Swanson - Tilera
    • Visualization, Multicore, Eclipse/CDT Redistribution
  8. Doug Schaefer - QNX
    • Everything, but currently working on improving Qt support
    • Also if we don't get many more people, we can meeting in one of the evenings as well
  9. Jeff Johnston - RedHat
  10. Jim Adams - Analog Devices
  11. Reibert Arbring - Ericsson
  12. Norman Yee - Analog Devices
  13. Leo Treggiari - Intel
  14. Vladimir Prus - Mentor Graphics
  15. Eric Cloninger - Klocwork
    • Static analysis, refactoring, Android
  16. Mike Wrighton - Mentor Graphics
  17. Greg Watson - IBM
  18. Brian Watt - IBM
  19. Teodor Madan - Freescale
  20. Jesper Eskilson - IAR Systems
    • MBS, TCF, indexer


  • Eclipse 4.x discussion:
    • reactions to 4.x platform
    • CDT compatibility and/or upgrade plans
    • effect on other projects, Visualizer, etc.
      (e.g. if CDT retains 3.x compatibility, related plugins may need to as well)
  • Debug
    • Quick Launches (Local C/C++ App, Remote C/C++ App)
    • UI Junit tests: Dependency injection vs other CDT UI test techniques
  • Advertising new CDT features
    • Dialog popup with "Did you know?" and "Don't show this message again"
    • Other?
  • Remote/synchronized projects
  • ...


  • Introductions
    • 24 attendees from 14 companies
  • E4
    • What is the gain to start using E4 APIs?
      • Easier to modify the look of the UI -- No need to move CDT to E4 for that
      • Uniformity of the look and feel -- No need to move CDT to E4 for that
      • QNX feels the UI must be improved -- Does that require E4?
      • Once the CDT community agrees we can use E4 APIs, the decision to do so can be left to individual committers. There does not seem to be a reason we'd have to move all of CDT. We can instead take a joint E4 and 3.x approach.
    • Is there a reason to avoid all use of E4 APIs?
      • We want to keep CDT compiling on 3.x
      • We can re-discuss this requirement for the Luna release


  • CDT 8.2 (Kepler) will not use any E4 APIs to keep compatibility with 3.x.
  • CDT will be free to use any new Platform APIs as long as it is not an E4 APIs. This will allow others to put CDT and the necessary part of the platform on top of 3.x.
  • CDT will not commit to supporting 3.x as a platform.

Back to the top