On 25.04.2012, at 23:12, Greg Ercolano wrote: > On 04/25/12 13:42, Matthias Melcher wrote: >> Also, I got MinGW running. Only caveat: if the script fails, the .BAT still >> does not fail, hence the result is alway "success". Maybe anyone has an idea? > > Is there a way to see the BAT and SH scripts? > > Usually it's just a matter of preserving exit codes, eg: > > REM Run a command that returns an exit code > some_command -arg -arg > exit %ERRORLEVEL% -- do this right after to return the exit code > > Usually the absolute last command's exit code is returned > from a DOS script, but perhaps something as simple as an > extra blank line is enough to make it loose the exit code, > or even a REM.. hard to say. > > ERRORLEVEL is both a command and variable name in DOS, > and not that many years ago DOS's exit didn't even support > returning an exit code: > > http://groups.google.com/group/alt.msdos.batch/browse_thread/thread/d4360b8cf8effbaa/2273bdd747fd50ea?hl=en&q=DOS+exit+code+ercolano#2273bdd747fd50ea > > I really liked the 'use assembly language' suggestion.. %^U
It's currently: C:\MinGW\msys\1.0\bin\sh.exe --login -c "( cd /c/jenkins/workspace/FLTK_1.3_MSVista_MinGW && date && gcc --version && autoconf && ./configure && make && date ) || set ERRORLEVEL=1" But looking at the console output, you should also see the echo: ... [FLTK_1.3_MSVista_MinGW] $ cmd /c call C:\Users\matt\AppData\Local\Temp\hudson3665012925727700183.bat c:\jenkins\workspace\FLTK_1.3_MSVista_MinGW>C:\MinGW\msys\1.0\bin\sh.exe --login -c "( cd /c/jenkins/workspace/FLTK_1.3_MSVista_MinGW && date && gcc --version && autoconf && ./configure && make && date ) || set ERRORLEVEL=1" Wed Apr 25 19:27:00 GMT 2012 gcc.exe (GCC) 4.6.2 Copyright (C) 2011 Free Software Foundation, Inc. ... _______________________________________________ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
