Hi!
22-Дек-2004 16:41 [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote to
[email protected]:
>> KD> +if "%COMPILER%" == "WATCOM" set LINK=call ..\utils\wlinker /nologo
>> Why?
jo> The current setup causes my command windows to exit on most
jo> compile errors, and that was from me trying to figure out what's
jo> up (at that time, I think it was a link issue).
Ok. First, "call" presence/missing doesn't affect calls throug
makefile, "call" affects execution only througb batch files. Second, you may
just remove check on "Close window on program exit" option. Third, you may
redirect output of (almost) all messages into external file. Example of my
batch file:
______________O\_/_________________________________\_/O______________
@ndos/e:2048 /c build %&
@beep
_____________________________________________________________________
O/~\ /~\O
There increased environment and given `beep' at compilation end without
modifying original batch files. NDOS itself allows to redirect output of
batch files. Under command.com, you may do so:
%comspec% /c build %1 %2 %3 %4 >compile.msg
I myself _always_ redirect output and always compare it with previous
results.
jo> It finally occurred to
jo> me that the watcom makefile is using the DOS and not NT hosted tools,
And? Which difference there?
jo> will be reverted when I get a chance. Still haven't figured
jo> out how to select NT or DOS watcom tools with the dev makefiles...
Use different config.bat with different pathes?
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Freedos-kernel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
