@also: Is it possible to add some details about your build command/env. ? ....
of course. All programming is done under win with slickedit for different hardware platforms.
An example for a command looks like this:
rsh servername -l username -n bin/arm-tools kernel_v6.xx AT91SAM9-M10 arm-angstrom-linux-gnueabi makeall
rsh is the win_remote_shell_client
It connects to rsh on servername, which may run on win, linux or the target itself, dependently on desired target platform.
then execute bourne_script arm-tool within desired ~/home defined with the username
and some arguments to the script arm-tools like workspacename, used controller, preferred compiler, toolchain_infos, etc.
We use controllers based on arm,cris,microchip, etc. but also PLD's must fit into this environment.
In the example above it simply executes a make all for desired hardware with the choosen compiler_tools
The result is written into a file with 'tee' and can be written into a database later.
Slickedit with the workspace->project configuration possibilities and tools unify all this things.
In the meantime errorparsing works well. The problem was the rsh_server on the windows platform and mingw.
Now the build results are written into a file AND send to the slickedit_shell from all platforms.
However, this can only be a temporary solution, but it works for now.
Tomorrow the programmers will have to use slickedit in place of codewright.
If something is not like they are used to, this guys pull my skin off.
Thank you very much for help!
also