[cdt-dev] Suggestions and questions regarding the CDT Builder Design

[Judy Green <jgreen@xxxxxxx>]

Hi folks,

A few of us were talking about the API for the CDT Core today.

We had some questions about what the Builder should look like and how this
information should be stored.
We realized that this will be impacted by what requirements others have on
the Builder(s)


We will be creating a '.cdt_project' xml file that will hold project
specific information (contents of the ICProjectDescription) in addition to
the familiar extension points defined in the 'plugin.xml' file. 

As you may know we will be providing an interface that will allow ISVs and
users to specify which component(s) they want in their projects.

Components that can be replaced by an ISV include:

Builder(s)
CoreModel (including the CDOM, Parsers etc)
BinaryParser
ArchiveParser
Indexer
CDOM

Pretty straight forward so far.

The Eclipse architecture allows multiple Builders to be associated with a
Project.
For a C/C++ Project, we need to be able to refine the steps that are
required to build. 
We need to be able to define what order they are built in.
We also need to provide hooks between the steps in order to do operations as
required.


For instance:

Step 1. Preprocess
Step 2. ??
Step 3. make
...
Step n. ??


We could predefine the steps and skip any that do not have operations
associated with them 
e.g.
<Builder={Preprocessor,,make,,}>

... or

We could provide a list, which is called in the order supplied in the
.cdt_project file

e.g. 
<Builder={PreProcessor, Make}>

... or
	Other suggestions?

-Judy

¨¨¨°ºo§oº°¨¨¨¨°ºo§oº°¨¨¨¨°ºo§oº°¨¨¨¨°ºo§oº°¨¨¨
Judy N. Green               Software Engineer
QNX Software Systems Ltd.   www.qnx.com
¨¨¨°ºo§oº°¨¨¨¨°ºo§oº°¨¨¨¨°ºo§oº°¨¨¨¨°ºo§oº°¨¨¨