share code between makebuilder and external scripts

Niko Sams niko.sams at
Wed Sep 22 18:23:42 UTC 2010

On Tue, Sep 21, 2010 at 23:03, Milian Wolff <mail at> wrote:
> Hey guys,
> I need your feedback on this. Apparently some people are using my external
> scripts plugin to run some magic build scripts, like e.g.:
> This is great since that was definitely one of the reasons I wrote that plugin.
> Anyways, people are not yet satisfied and want (rightly so!) the features we
> give them for plain make build jobs, esp. the highlighting of errors/warnings
> and the ability to jump to those positions inside the code.
> I want to give that to the users of custom buildsystems as well, currently I'd
> imagine a checkbox in the configuration of an external script, which you can
> tick to enable this "error detection".
Very good idea, I even have my own (very special) use case:
In Quanta3-days I had a shell script that that opened a connection to
firefox, parsed the
current site for errors and backtraces and displayed them in a kdialog
combobox. Then I
could select a line and that line was opened in the editor (using DCOP).
With that "error detection" feature I could use my script again :D
As you see, people do weird things - and that special use case can't be solved
using a custom make target imho. At least not with a usable ui.

And, one more thing: It would also make sense to have this "error
detection" for Launches.
When using ExecuteScript to execute a php script you usually get
backtraces directly
on stdout.

Oh, and mabye not "error detection" but "filepath detection". Think of a special
grep or something.


More information about the KDevelop-devel mailing list