Hi
Viktor Szakáts wrote: > > Yes of course, just use the regular method shown for > Harbour builds in INSTALL doc examples. > > It's '> log.txt 2>&1' but rather check it for yourself. > > Or create batch file: > --- log.bat > %* > log.txt 2>&1 > --- > > And use: > log hbmk2 ... > > Both stdout and stderr output will be in log.txt > >> Then I increased the console's buffer to 500 from 25 and then I could >> visualize what these errors are. > > You can use -beep option, which will double beep on errors > and single beep when everything is OK. Notice you won't > hear the beep if your redirect the output, like above. > > And there is also -pause option, which will wait for a key > in case of error, so you can read it from the console. > For -pause to work you need to override gt to native console > gt because hbmk2 default gtcgi doesn't support keyboard: > --hb:gtwin -pause (on Windows) > Now I think I am begining to understand hbmk2 more closely. Nice features. BTW I get these unresolved externals in MINGW build, MSVC and BCC is ok. C:/harbour_dev/harbour/mingw/lib/libhbziparc.a(hbziparc.o):hbziparc.c:(.data+0x9 8): undefined reference to `HB_FUN_HB_UNZIPOPEN' C:/harbour_dev/harbour/mingw/lib/libhbziparc.a(hbziparc.o):hbziparc.c:(.data+0xa 8): undefined reference to `HB_FUN_HB_UNZIPGLOBALINFO' C:/harbour_dev/harbour/mingw/lib/libhbziparc.a(hbziparc.o):hbziparc.c:(.data+0xb 8): undefined reference to `HB_FUN_HB_UNZIPCLOSE' C:/harbour_dev/harbour/mingw/lib/libhbziparc.a(hbziparc.o):hbziparc.c:(.data+0xe 8): undefined reference to `HB_FUN_HB_UNZIPFILEFIRST' C:/harbour_dev/harbour/mingw/lib/libhbziparc.a(hbziparc.o):hbziparc.c:(.data+0xf 8): undefined reference to `HB_FUN_HB_UNZIPFILEINFO' C:/harbour_dev/harbour/mingw/lib/libhbziparc.a(hbziparc.o):hbziparc.c:(.data+0x1 28): undefined reference to `HB_FUN_HB_UNZIPFILENEXT' C:/harbour_dev/harbour/mingw/lib/libhbziparc.a(hbziparc.o):hbziparc.c:(.data+0x1 e8): undefined reference to `HB_FUN_HB_ZIPOPEN' C:/harbour_dev/harbour/mingw/lib/libhbziparc.a(hbziparc.o):hbziparc.c:(.data+0x2 78): undefined reference to `HB_FUN_HB_ZIPFILECREATE' C:/harbour_dev/harbour/mingw/lib/libhbziparc.a(hbziparc.o):hbziparc.c:(.data+0x2 a8): undefined reference to `HB_FUN_HB_ZIPFILEWRITE' C:/harbour_dev/harbour/mingw/lib/libhbziparc.a(hbziparc.o):hbziparc.c:(.data+0x2 c8): undefined reference to `HB_FUN_HB_ZIPFILECLOSE' C:/harbour_dev/harbour/mingw/lib/libhbziparc.a(hbziparc.o):hbziparc.c:(.data+0x2 e8): undefined reference to `HB_FUN_HB_ZIPCLOSE' C:/harbour_dev/harbour/mingw/lib/libhbziparc.a(hbziparc.o):hbziparc.c:(.data+0x3 18): undefined reference to `HB_FUN_HB_UNZIPEXTRACTCURRENTFILE' C:/harbour_dev/harbour/mingw/lib/libhbziparc.a(hbziparc.o):hbziparc.c:(.data+0x3 58): undefined reference to `HB_FUN_HB_ZIPDELETEFILE' collect2: ld returned 1 exit status hbmk2: Error: Running linker. 1 Are these functions disabled for MINGW? Is there any alternatives to above functions ? If not, I am afraid it may stop my experiments with GTWVG and HBXBP together as all will be tested under production-like environments. Regards Pritpal Bedi -- View this message in context: http://www.nabble.com/HBMK2---Strange-Behavior-tp25107808p25111800.html Sent from the Harbour - Dev mailing list archive at Nabble.com. _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
