RE: [cdt-dev] CDT Build Console enhancements

[<Warren.Paul@xxxxxxxxx>]

It sounds like he just wants to add the same build toolbar to the console view which sounds fine.  I don't like add command line arguments for make to the standard CDT build console since there are many other non-make based builders.  That could potentially be added dynamically based on the type of project being built.

Hyperlinks of errors/warnings in the console view would be a great addition IMO.  There's actually a bug (or two or three) about this with a good amount of history.  I would recommend tracking that down so you can see whatever issues you might run into.  I remember looking at doing that a year or two ago and ran into some problems that couldn't be solved without a decent refactor of the CDT build console.

As James said, anything to do with parsing errors and resolving source locations should be done in the error parsing mechanism so the results are the same in both the console and problems view.

Thanks,
Warren
 

>-----Original Message-----
>From: cdt-dev-bounces@xxxxxxxxxxx 
>[mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of ext James Blackburn
>Sent: Monday, October 19, 2009 10:44 AM
>To: CDT General developers list.
>Subject: Re: [cdt-dev] CDT Build Console enhancements
>
>Hi Dmitry,
>
>2009/10/19 Dmitry Kozlov <ddk@xxxxxxxxxxxxxxxx>:
>> I'm working on some enhancements to CDT Build Console:
>> - Run build button on concole toolbar, to run build directly from 
>> console
>
>How would this differ from the BuildAction in the toolbar or 
>make targets in the make target view?
>
>> - "Make arguments" text field on console toolbar to pass 
>parameters to 
>> make when Run build is pressed
>> - Build Console output text partitioning to enable moving between 
>> errors and going from errors to source code directly from 
>console, not 
>> using problems view.
>
>This sounds useful.
>
>> - File prefixes translation in console preferences to enable view 
>> error in local source file while compiler reported error against 
>> remote filesystem, e.g. translate /net/user/project/src/ to 
>C:\myProject\src.
>
>This should be part of the ErrorParser framework, or there'll 
>be a confusing disconnect between what the console is able to 
>do and what the Problems view gives.  There's also no point 
>re-implementing the source resolution logic.
>
>I'm not sure how much of the above belongs in the Console. The 
>builds have (so far) been run using the Eclipse project 
>builder mechanism.
>Arguably, for Makefile projects, this is overkill as we don't 
>care about resource deltas since last build and it's a pain 
>having the Workspace locked.  How would a console run build be 
>different from the existing build mechanisms we've got?
>
>Cheers,
>James
>
>> - Save console to file button on console toolbar.
>>
>> I suppose it is better to do it as existing console build 
>modification 
>> instead of writing plugin with another console implementation. Can 
>> these modifications be included to CDT head? Who can help 
>with review 
>> code and commiting this?
>> Any other suggestions concerning this functionality from CDT team?
>>
>>
>> Best regards,
>> Dmitry Kozlov
>>
>>
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>
>_______________________________________________
>cdt-dev mailing list
>cdt-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/cdt-dev
>