A few fixes to make Windows Mojo build work.

A few fixes to make Windows Mojo build work.

R=scottmg@chromium.org

Committed: https://chromium.googlesource.com/external/mojo/+/726443c943af9eda16621199a9d2144c42984bbb

[jam, 2014-11-08 03:16:50]

jam@chromium.org changed reviewers:
+ scottmg@chromium.org

[jam, 2014-11-08 03:16:51]

The first three files are a merge from your chromium cl
https://codereview.chromium.org/709793002

[scottmg, 2014-11-08 03:22:27]

lgtm

https://codereview.chromium.org/685203004/diff/1/mojo/tools/mojob.py
File mojo/tools/mojob.py (right):

https://codereview.chromium.org/685203004/diff/1/mojo/tools/mojob.py#newcode64
mojo/tools/mojob.py:64: 
if you add 

if platform.system() == 'Windows' and os.path.isdir(out_dir):
  shutil.rmtree(out_dir)

it'd probably build ok (plus import shutil at top)

[jam, 2014-11-08 03:23:51]

https://codereview.chromium.org/685203004/diff/1/mojo/tools/mojob.py
File mojo/tools/mojob.py (right):

https://codereview.chromium.org/685203004/diff/1/mojo/tools/mojob.py#newcode64
mojo/tools/mojob.py:64: 
On 2014/11/08 03:22:27, scottmg wrote:
> if you add 
> 
> if platform.system() == 'Windows' and os.path.isdir(out_dir):
>   shutil.rmtree(out_dir)
> 
> it'd probably build ok (plus import shutil at top)

I wanted to do that in the recipe script so that it doesn't happen locally if
i'm using a version of ninja that doesn't have the bug..

[scottmg, 2014-11-08 03:25:17]

sgtm (I couldn't get mojob.py to run locally, but that was probably because of
the get_out_dir() change you made...)

[scottmg, 2014-11-08 03:25:34]

On 2014/11/08 03:25:17, scottmg wrote:
> sgtm (I couldn't get mojob.py to run locally, but that was probably because of
> the get_out_dir() change you made...)

or rather, fixed by the change you made

[jam, 2014-11-08 03:27:06]

Committed patchset #1 (id:1) manually as
726443c943af9eda16621199a9d2144c42984bbb.