On Wed, Jul 21, 2010 at 3:11 PM, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote:
On Wed, Jul 21, 2010 at 12:23
PM, Andrew Gvozdev <angvoz.dev@xxxxxxxxx>
wrote:
> On Wed, Jul 21, 2010 at 11:52 AM, Doug Schaefer <cdtdoug@xxxxxxxxx> wrote:
>> The idea is that the build console is independent of whatever build
>> system you are using.
> I agree with this statement and think everybody does. The moving does not
> introduce dependency from build console to MBS. I think de-facto
> org.eclipse.cdt.make encompass build functionality common for all build
> systems in general.
I'm not sure that's true. That's my point. I believe there are
commercial products out there that don't use CDT's build system at
all, including cdt.make.
I suppose you are worrying
about the case when the vendors use their own builder (i.e. modified copy of
cdt.make.core.MakeBuilder)? I don't believe it would ever break these. The
console is still contributed via extension point
org.eclipse.cdt.core.CBuildConsole in cdt.core and CCorePlugin.getConsole()
will pull it from whatever plugin contributed the console.
Andrew
>
> Do you see the package as being specific to Standard Make build? In this
> case, would you agree to create a new package encompassing general build
> functionality and move there the build console and generalized build
things
> from the other package?
>
> Andrew
>