[cdt-dev] Wrapping CDT command invocation

[James Blackburn <jamesblackburn@xxxxxxxxx>]

Hi All,

I'm currently looking into the best way to transparently wrap CDT
command invocation so that I can tweak the command before invoking it.
 The reason is I'd like to prepend 'bsub -I <command>' to submit the
commands to a LSF queue, though you could imagine using 'ssh / rsh' to
cause the command to be executed on another machine.  I imagine this
is the sort of thing that RDT needs to do as well.

I've seen 'CommandLauncher' though this only appears to be used by
build.  I also found a presentation detailing RDT's service model, but
I can't quite figure out how this fits into CDT (if it does at all).
Ideally my process runner wrapper would be othogonal to Building or
Launching. The user would have some UI to control which long running
tasks they wanted to wrap, which could be set at the Workspace or
Project scope. They would have one place where they could configure
their command wrapper, the running of which would be transparent to
the component executing the external tool.

Is there a clean way of doing this already?  Is there some mechanism /
project that I've missed that adds this functionality?

Any pointers greatly appreciated.

Cheers,
James