On 25.04.2012 01:09, Ian MacArthur wrote: > > On 23 Apr 2012, at 22:52, Matthias Melcher wrote: >> >> Oh, and a second thing: I am also trying to find a way to run MinGW scripts >> from the MSWindows shell (which is what Jenkins does). > > OK, on my VM that has "current" mingw I did "mingw-get update" to make sure > all was current,
That's not true, "mingw-get update" only loads the new "manifest" files, i.e. the package definitions and dependencies (mingw-get is modelled like apt-get). It's not yet full-featured, but you can now upgrade individual packages with all dependencies, i.e. mingw-get upgrade gcc etc., and you can upgrade all packages w/o a package specification: mingw-get upgrade Just tested, this *seems* to work (after mingw-get update, of course). However, due to a possible bug in mingw-get this could only show that it updates (some) packages, but not really do it :-( > Also, I find I can trigger the build form a "DOS shell" with the following > dos batch file: > > ------ > REM does this work? Apparently it does! > > D:\MinGW\msys\1.0\bin\sh.exe --login -c "cd /d/source/fltk-1.3 ; make" > ------ > > I assume that Jenkins could run this (or a suitably path-corrected) bat file > and trigger the mingw command line build that way? Good to know how it works exactly, thanks for testing. Albrecht _______________________________________________ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
