> Nothing. That is because mpasmwin does not write the errors to stdout but
to
> a file. Textpad capture the stdout output, but not the file, the
> double-click only works in the captured output from stdout.
>
> I have just made this work-around:
>
> Create this batch file and save it in c:\mpasm\mpasm.bat, (use the
directory
> you want):
>
>     @echo off
>     c:\mpasm\asm21500\mpasmwin %1 %2 %3 %4 %5 %6 %7 %8 %9
>     type c:\temp\mpasm.err
>
> Take care to change the path where you have mpasmwin installed and where
you
> want the error file, mpasm.err, to be written.
>
> Now, instruct textpad not to run mpasmwin but this mpasm.bat file. You
have
> to pass the parameter /e pointing to the error file you are going to
"type"
> in the mpasm.bat file (c:\temp\mpasm.err) in this case.
>
> The "problem" here is that you don4t have a .err file for each file you
> compile.

Even easier, just use my ASMPIC program
(http://www.embedinc.com/pic/asmpic.txt.htm).  This is a wrapper around
MPASMWIM that makes it look just like a real tool.  Among other things, it
causes the error messages to be written to standard output and sets a proper
exit status code so that the envoking program can easily determine
success/failure.  For the bigger picture, check out the "PIC assembler build
tools" section at the bottom of http://www.embedinc.com/pic.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body