Uwe: buildtool builds on a best effort basis, trying to compile everything it can before stopping. To see the errors, you need to run buildtool again; it will only try to rebuild the files that had errors. You can capture this log to a file by running buildtool like this: buildtool 2> log.txt
Last time I used it, before the new devlibs which shouldn't have changed anything, buildtool writes its output to a file already; the filename was compile.lst or something like that. Also on Windows 2> won't work; that would run "buildtool 2" and put its output in log.txt. It would be buildtool > log.txt or buildtool>log.txt for Windows. stderr will be caught automatically, I believe. Windows' separation of them is less precise than other operating systems'.
Regards,
Chris Morgan