Adding GYP V2 targets for all Polymer code (with a script!).

Adding GYP V2 targets for all Polymer code (with a script!).

... a nodeJS script... see gendeps.js.

BUG=

[dpapad, 2016-02-13 03:20:53]

Description was changed from

==========
Adding GYP V2 targets for all Polymer code (with a script!).

... a nodeJS script...

BUG=
==========

to

==========
Adding GYP V2 targets for all Polymer code (with a script!).

... a nodeJS script... see gendeps.js.

BUG=
==========

[Dan Beam, 2016-02-16 07:01:08]

https://codereview.chromium.org/1695663004/diff/1/third_party/polymer/v1_0/ge...
File third_party/polymer/v1_0/gendeps.js (right):

https://codereview.chromium.org/1695663004/diff/1/third_party/polymer/v1_0/ge...
third_party/polymer/v1_0/gendeps.js:39: var regexp = /^<link rel="import"
href="(.*)"/;
BeautifulSoup is a better candidate for this, IMO:
https://codereview.chromium.org/1702553002/

[dpapad, 2016-02-16 18:59:16]

On 2016/02/16 at 07:01:08, dbeam wrote:
>
https://codereview.chromium.org/1695663004/diff/1/third_party/polymer/v1_0/ge...
> File third_party/polymer/v1_0/gendeps.js (right):
> 
>
https://codereview.chromium.org/1695663004/diff/1/third_party/polymer/v1_0/ge...
> third_party/polymer/v1_0/gendeps.js:39: var regexp = /^<link rel="import"
href="(.*)"/;
> BeautifulSoup is a better candidate for this, IMO:
> https://codereview.chromium.org/1702553002/

Tried to keep third-party Node dependencies to a minimum (currently only using
"glob"). There are a few HTML
parsers for Node too, (cheerio, and port of BeautifulSoup node-soupselect), but
the regexp seems to be good
enough, no need to fully parse the file to extract it.

Either way would you be OK if I remove the gendeps.js script from this CL and
land the compiled_resources2.gyp files?
We can decide separately about how to move forward with the script (node vs
python, and which 3rd party deps).