[Qt-creator] customized make & clean

[Daniel Teske]

> =============
> on MS-Windows:
> =============
> 1. if customized make command (see
> http://lists.trolltech.com/pipermail/qt-creator/attachments/20090618/225f2c
>cf/attachment-0001.png) is realized as a script (actually 'remote.ssh.bat'),
> it cannot be found although the build environment includes correct PATH,
> PATHEXT settings. unfavorable workarounds are: use absolute path (actually 
> C:\WINNT\system32\remote.ssh.bat) or compile .BAT to .EXE

We aren't a shell, if you want to run a .bat file you need to run cmd.exe /c 
(or cmd.exe /k). I have no idea why it actually works with the complete path, 
maybe the windows api then runs the default program associated with .bat

> 2. our customized make command does a remote-compile on a Linux host (see
> attachment win-build-issues.png). Errors are marked red in the 'Compile
> Output', but the 'Build Issues' remains EMPTY. I guess you filter build
> issues from STDERR? I know, it's ugly, but could you perhaps apply the
> Linux filters also on MS-Windows?
> [cid:bf34b1c6-ef0b-46ea-979c-66f3bf053750]
There are a few things which don't work for you:
a) We do only read STDERR
b) We know which compiler was used for the qt version in Tools\Qt-Version, and 
use the corresponding build parser. So if you want a gcc parser, you need to 
lie about the qt version.
c) We parse the filenames from the output, which probably doesn't work for you.


What I would rather do is this, and I actually have most of that planned:

-  Make the BuildSteps "qmake" and "make" optional.
-  Add a option to have the output of a custom process step parsed by a
   buildparser (and let the user choose freely.)
-  Possibly with file path munging afterwards

That should be enough for most remote building setups.

The only problem is then, to set it up correctly, since the default build set 
up is hardcoded, in qt4project.cpp


daniel