Building chromium with msvs-ninja as GYP_GENERATOR will emit angle/third_party warnings

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Have a chromium checkout.
2. Have msvs-ninja in your GYP_GENERATORS
3. Run python build/gyp_chromium.py

What is the expected output? What do you see instead?

I expect a clean build of project files. Instead there are about 60 warnings 
about files mentioned in gyp files that don't exist.

Most of them are from angle:

src\third_party\angle\tests\third_party\googlemock\src\gmock-all.cc

src\third_party\angle\tests\third_party\googletest\src\gtest-all.cc

src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\allocators.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\document.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\encodedstrea
m.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\encodings.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\error\en.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\error\error.
h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\filereadstre
am.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\filestream.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\filewritestr
eam.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\internal\dto
a.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\internal\ito
a.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\internal\met
a.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\internal\pow
10.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\internal\sta
ck.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\internal\str
func.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\memorybuffer
.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\memorystream
.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\msinttypes\i
nttypes.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\msinttypes\s
tdint.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\prettywriter
.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\rapidjson.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\reader.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\stringbuffer
.h
src\third_party\angle\tests\third_party\rapidjson\include\rapidjson\writer.h

These libraries are optional libraries used for testing so options could be:

* Move them into the angle tree.

* Check them out when chromium is checked out (requires moving to other git 
servers).

* Cut off all references of them when chromium is built.

* Something else.

Original issue reported on code.google.com by brat...@opera.com on 24 Feb 2015 at 5:30

[GoogleCodeExporter]

This is tracked on the chromium side in 
https://code.google.com/p/chromium/issues/detail?id=459058

Original comment by brat...@opera.com on 24 Feb 2015 at 5:32

[GoogleCodeExporter]

Original comment by jmad...@chromium.org on 24 Feb 2015 at 5:51

[GoogleCodeExporter]

Original comment by jmad...@chromium.org on 24 Feb 2015 at 5:52

• Changed state: Started

[GoogleCodeExporter]

Should be fixed now.

Original comment by jmad...@chromium.org on 9 Mar 2015 at 6:24

• Changed state: Fixed