Now I know what are the errors. Infact the above process do not record link errors in the log file and on a console of 25x80 these are scrolled so fast that you cannot catch-up. Is there a way to get those errors also logged to log file ?
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)
Thanks for your patience for analysing my script.
You're welcome! Brgds, Viktor _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
