[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cdt-core-dev] CDT core plan
|
Hi, all!
As I have said already in cdt-debug we in Interstron Ltd (www.interstron.com) would use CDT under Win 2000 using Cygwin and gdb 5.2.1. I want to repeat it there in cdt-core and also want to say that supporting of Cygwin will be great for us because we planning to use Project managment GNU utils a lot(automake, autoconf) and maybe we will make some contribution in these theme.
Thanks,
Garra, isz@xxxxxxxxxxxxx
Interstron Ltd.
www.interstron.com
>Hi all,
>
>here's the draft plan for the CDT core and UI components.
>The plan is split into 3 major "releases", which align
>with the debugger/launcher plan. The first is in
>october, as the first, working prototype implementation, the
>second is targetted for march 2003, and the third for august 2003.
>
>** October 2002 **
>
>The focus is on cleaning up the QNX CDT code and doing all
>of the 2.0 catchup items, as well as adding features to
>support the modularity and overridability of the CDT components.
>
>
>
>** March 2003 **
>
>Based on the experience and feedback gathered with the october
>release, we will finalize the public interfaces for the parser,
>indexer and C model. This is also the target for adding code
>formatting support, as well as a prototype of the CDOM.
>
>
>** August 2003 **
>
>Feature set for this will be determined by the feedback and direction
>that the CDT takes.
>
>
>
>** Detailed work items for October 2002 **
>
>CDT Core
>
>Supported platforms:
>- Linux w/gdb 5.2.1
>- QNX w/gdb 5.2.1
>- Maybe windows with cygwin and gdb 5.2.1 (need someone to take
>ownership)
>
>
>C component manager
>- manages the selection of which components to use for a project.
>- allows overriding the default CDT implementation (e.g. replace the
>builder)
>
>2.0 catchup items
>- clean up extension points
>- bring editor to 2.0 GA level
>- bring menu handling to 2.0 level
>- clean up deprecated function warnings
>
>Provide prototype versions of CDT API's
>- C model
>- Indexer interface
>- Parser interface
>- Help integration interface
>
>Prototype version of builder (simple builder model)
>
>Improve indexer
>- bound amount of memory used
>- save indexing info to file for persistence
>
>Project conversion wizards
>- convert from generic to C/C++ project
>- convert from C to C++
>
>Additional preferences
>- component arguments/settings
>- formatting preferences
>
>The last two items are currently unassigned and will probably
>not get done:
>
>C search page
>Class browser
>
>
>As well, we are lacking user documentation, due to resourcing
>constraints.
>
>====================================================================
>
>Please review and comment on the plan. Also remember that if there's some
>feature that you'd like to see added, you help would be very welcome!
>
>The CDT core team
>_______________________________________________
>cdt-core-dev mailing list
>cdt-core-dev@xxxxxxxxxxx
>http://dev.eclipse.org/mailman/listinfo/cdt-core-dev