Thank you guys for your interest and for many useful ideas. I want to
sum up all questions and comments and provide some answers.
1. Run build button from console. I just trying to reuse existing build
mechanism as it is used in TargetBuild class.
2. I will make preference in build console whether to show make
arguments text field. If you can tell me for what kind of projects it
should be enabled/disabled please advice and I will make this determined
automatically.
These make args provided by user are not used to update project
configuration but work as one-shot deal just for make which is run
pressing Run Build button at console toolbar.
3. Saving console now is implemented as saving current console content
but not full build output. It is very good idea to use tee. I will take
a look at this. Olexiy, you can help with this if you want.
4. I want to reuse error parsers to partition console output, but this
is not implemented yet. I'm familiar with 50124 implementation and I
will look at 203727, many thanks for this information. I'm not intended
to use my own error parsing as it is done in 50124.
It is the general answers, but there are some technical problems which I
want to discuss separately:
1. There a problem with TargetBuild: it is from cdt.make.ui, but console
is in cdt.ui so using this results cyclic dependency between cdt.make.ui
and cdt.ui because cdt.make.ui already depends on cdt.ui. In my current
prototype implementation I copypasted TargetBuild to cdt.ui and
slightly modified it. Are there other ideas how to cope with this
without copy-past?
2. To partition console output according errors I expected to reuse
markers at Problems view, created by existing error parsers, but I
failed to find public API to markers and this code unfortunately is part
of platform, not the CDT. So there are 2 questions: 1) any idea how to
do this without platform modification, 2) is it easy to check in
appropriate platform modification motivated by needs of CDT project, can
somebody help with lobbying this?