March 16, 2014 Re: Get Compile Errors - Command Line | ||||
---|---|---|---|---|
| ||||
Posted in reply to Bauss | On Sunday, 16 March 2014 at 13:57:42 UTC, Bauss wrote: > Actually I was doing it through C#. I have tried getting the output of the window but it doesn't seem to redirect it. Did you try the startup info there too? Here's a link with a .net example: http://stackoverflow.com/questions/4291912/process-start-how-to-get-the-output Notice that the answer itself only redirects the output, but dmd I believe uses the error stream for it. The comments discuss it: add to the ctor: RedirectStandardError = true, and read from proc.StandardError afterward. |
March 17, 2014 Re: Get Compile Errors - Command Line | ||||
---|---|---|---|---|
| ||||
Posted in reply to Adam D. Ruppe | On Sunday, 16 March 2014 at 18:45:30 UTC, Adam D. Ruppe wrote:
> On Sunday, 16 March 2014 at 13:57:42 UTC, Bauss wrote:
>> Actually I was doing it through C#. I have tried getting the output of the window but it doesn't seem to redirect it.
>
> Did you try the startup info there too? Here's a link with a .net example:
>
> http://stackoverflow.com/questions/4291912/process-start-how-to-get-the-output
>
>
> Notice that the answer itself only redirects the output, but dmd I believe uses the error stream for it. The comments discuss it:
>
> add to the ctor:
> RedirectStandardError = true,
>
> and read from proc.StandardError afterward.
Thank you! That was the issue. I was reading from the standardoutput and not standarderror
|
Copyright © 1999-2021 by the D Language Foundation