[cdt-core-dev] [Bug 25756] gcc output -> tasks conversion is broken (fwd

["Alain Magloire" <alain@xxxxxxx>]

> 
> 
> ------- Additional Comments From d92-jwa@xxxxxxxxxxx  2002-11-06 12:15 -------
> I still think the first two tasks shouldn't be there at all:
> 
> A requirement for turning something into a task should be that it has a file
> name and a line number associated with it.  Makefile errors (for your example)
> are reported like this:
> 
> Makefile:1: *** missing separator.  Stop.
> 
> Thus, they come with a (Make)file name and a line number.  Anything else are
> just indicators that make has received an error code, which should be obvious
> anyway from the output of the failing command.
> 


This is more suitable in this mailing list.


There is now a MakeErrorParser, watching the output of the build, the goals
are :

1) Watch the output for key words like "Entering Directory..."
  "Leaving Directory"  to help the ErrorParserManager when searching for resources
  to set error markers(taks).

2) Detect Makefile errors, things like:
  all
	gcc -o hello hello.c -g
  Makefile:1: *** Missing separator

3) General build errors:

  all:
	some_script_that_will_fail
make
 some_script_that will fail ooutput
make: *** [all] Error 2

  In this case, we need to mark that build failed.  But there is no clue
  in parsing the output that things failed.  Only make will show that target
  "all" was an error.  It is shown in the task view and the Resource is on the
  project.


  The side effect of this is that if the error is recognise you will have
  two errors.  IMHO, it is not that bad?