[Win] Make build logs more legible by reducing noise

• Component: WebCore Misc.
• Status: RESOLVED FIXED

[Brent Fulgham]

Our Windows build logs produce a tremendous amount of boilerplate output and detailed build state that makes it very difficult to find and understand why the build has failed.

We can improve things as follows:

1. Update our batch file (Windows CMD files) to use the '@' character as the first character on each line. This will prevent these lines from being echoed into our build logs.
2. Pass the '/Q' flag to our invocations of CMD so that they run silently. This will reduce another set of output that we generally do not care about.
3. Pipe the output of XCOPY to "NUL". This will hide the file copy state, but we have not generally found these messages to be helpful when debugging build errors, even when they have been caused by files not being copied.

[Brent Fulgham]

Created attachment 247410 [details]
Patch

[Brent Fulgham]

The patch seems to be failing on the Windows EWS bot, I believe due to EOL differences. 

Unfortunately, I can't tell from the log (which is ironic, since the point of this patch is to fix this problem).

[Alexey Proskuryakov]

Comment on attachment 247410 [details]
Patch

rs=me

[Brent Fulgham]

Committed r180676: <http://trac.webkit.org/changeset/180676>

[Brent Fulgham]

I missed an important set of changes to {Pre|Post}{Build|Link} steps. This was committed in r180680 <https://trac.webkit.org/changeset/180680>.

[Radar WebKit Bug Importer]

<rdar://problem/19985941>