Get `gn gen` to succeed on Windows

Get `gn gen` to succeed on Windows

1. Pull in NSS for net, crypto
2. Copy sqlite from chromium for NSS
3. Some mucking in build/ to avoid DEPSing gyp
4. Pull in gperf and bison on win

I believe 1&2 can be deleted later once net is moved out.

This gets as far as successful project generation, and builds a bunch
of stuff but there's still quite a few compile errors.

Result of `ninja -C out\Debug root -k0 >log.txt` here:
https://gist.github.com/sgraham/7e58a022595db1c0ae60

They don't look too major, but I don't know if mojo wants to take on
longer term support/maintenance of Windows, with bots/etc. so not sure
this is worth it or not.

(To work fully this also requires a ninja binary at ninja ToT that's
not pushed to depot_tools yet. But the compile errors are unrelated,
and ninja will get there eventually.)

R=jam@chromium.org
BUG=

Committed: https://chromium.googlesource.com/external/mojo/+/d19529d27cdfff8a1a8d663828e5a927b08dcabf

[scottmg, 2014-11-03 21:04:49]

fyi

[scottmg, 2014-11-03 21:25:37]

Actually, after I DEPS bison and gperf, it's not terrible looking. ~10-20
linux-ism. Maybe the right time to do this is once net is moved out, though I
guess various things will rot more the longer you wait.

[jam, 2014-11-03 22:04:49]

lgtm, thanks!

re the ninja binary, I'm not sure what you mean that this needs a new binary but
the compile errors are unrelated?

On 2014/11/03 21:25:37, scottmg wrote:
> Actually, after I DEPS bison and gperf, it's not terrible looking. ~10-20
> linux-ism. Maybe the right time to do this is once net is moved out, though I
> guess various things will rot more the longer you wait.

The net stuff is going to happen, but I don't know when.

https://codereview.chromium.org/694353003/diff/10001/build/vs_toolchain.py
File build/vs_toolchain.py (left):

https://codereview.chromium.org/694353003/diff/10001/build/vs_toolchain.py#ol...
build/vs_toolchain.py:1: # Copyright 2014 The Chromium Authors. All rights
reserved.
ditto for all these updates to files in build?

https://codereview.chromium.org/694353003/diff/10001/build/win/win_tool.py
File build/win/win_tool.py (right):

https://codereview.chromium.org/694353003/diff/10001/build/win/win_tool.py#ne...
build/win/win_tool.py:1: #!/usr/bin/env python
are you going to check a copy of this to chromium as well?

[scottmg, 2014-11-03 22:28:34]

https://codereview.chromium.org/694353003/diff/10001/build/vs_toolchain.py
File build/vs_toolchain.py (right):

https://codereview.chromium.org/694353003/diff/10001/build/vs_toolchain.py#ne...
build/vs_toolchain.py:22: def NameValueListToDict(name_value_list):
This was also to avoid pulling gyp. Maybe I should just do that instead?

... hmm, actually, GYP_DEFINES doesn't make any sense in mojo so I'll just
delete that code instead.

https://codereview.chromium.org/694353003/diff/10001/build/win/win_tool.py
File build/win/win_tool.py (right):

https://codereview.chromium.org/694353003/diff/10001/build/win/win_tool.py#ne...
build/win/win_tool.py:1: #!/usr/bin/env python
On 2014/11/03 22:04:49, jam wrote:
> are you going to check a copy of this to chromium as well?

This was copied from gyp, so no. (GN currently uses it on Mac and Windows but
didn't make its own copy.)

[jam, 2014-11-03 22:36:50]

https://codereview.chromium.org/694353003/diff/10001/build/win/win_tool.py
File build/win/win_tool.py (right):

https://codereview.chromium.org/694353003/diff/10001/build/win/win_tool.py#ne...
build/win/win_tool.py:1: #!/usr/bin/env python
On 2014/11/03 22:28:34, scottmg wrote:
> On 2014/11/03 22:04:49, jam wrote:
> > are you going to check a copy of this to chromium as well?
> 
> This was copied from gyp, so no. (GN currently uses it on Mac and Windows but
> didn't make its own copy.)

i see. so when chrome is gn-only, then this file will be created there as well?

[scottmg, 2014-11-03 22:43:42]

On 2014/11/03 22:36:50, jam wrote:
> https://codereview.chromium.org/694353003/diff/10001/build/win/win_tool.py
> File build/win/win_tool.py (right):
> 
>
https://codereview.chromium.org/694353003/diff/10001/build/win/win_tool.py#ne...
> build/win/win_tool.py:1: #!/usr/bin/env python
> On 2014/11/03 22:28:34, scottmg wrote:
> > On 2014/11/03 22:04:49, jam wrote:
> > > are you going to check a copy of this to chromium as well?
> > 
> > This was copied from gyp, so no. (GN currently uses it on Mac and Windows
but
> > didn't make its own copy.)
> 
> i see. so when chrome is gn-only, then this file will be created there as
well?

Yeah, or something similar/simpler anyway.

[scottmg, 2014-11-03 23:05:03]

Committed patchset #3 (id:20001) manually as
d19529d27cdfff8a1a8d663828e5a927b08dcabf.