Applied [HEAD] Re: [cdt-patch] Scanner Interface for Managed and Standar

[John Camelon <jcamelon@xxxxxxxxxx>]

JohnC

Sean Evoy/Ottawa/IBM@IBMCA
Sent by: cdt-patch-admin@xxxxxxxxxxx

07/03/2003 05:27 PM

Please respond to
cdt-patch@xxxxxxxxxxx

To	cdt-patch@xxxxxxxxxxx
cc
Subject	[cdt-patch] Scanner Interface for Managed and Standard Build Models

Hi All, 
I will follow this up with a fairly detailed discussion about the changes
I have made to the standard build model and why, but I want to submit this
patch to unblock some of the indexing work that is about to start. The
change logs contain an overview of what has been done to implement a new
interface between a build model (any build model) and clients of the model
that need to extract include search paths and defined symbols. For the
most part, I have tried to leave the old build system as unchanged as possible.
For example, project properties like the make search path, and whether
or not to continue on build failures are still stored as persistent properties
on the project through the CNature (ugh). The new information I have added
is managed by a new build manager on a per-project basis and is associated
with a project as a session property. The information is persisted in the
'cdtbuild' file introduced by the new managed build system.

I smoke-tested the changes on Windows and Solaris.

Next week I will be removing all associations between the managed and standard
project natures, so you won't have both C/C++ Build and C/C++ Project property
pages for managed projects. 

Sean Evoy
Rational Software - IBM Software Group
Ottawa, Ontario, Canada[attachment "NewBuildManager.zip" deleted
by John Camelon/Ottawa/IBM] [attachment "cdt-ui-patch.txt" deleted
by John Camelon/Ottawa/IBM] [attachment "cdt-core-tests-patch.txt"
deleted by John Camelon/Ottawa/IBM] [attachment "cdt-core-patch.txt"
deleted by John Camelon/Ottawa/IBM]