Makes matching of build files work when absolute

Makes matching of build files work when absolute

Matching wasn't working if paths supplied were absolute. gyp_chromium
triggers absolute paths, so picking up modified gyp/gypi files wasn't
working when analyzer run from chrome.

BUG=109173
TEST=none
R=scottmg@chromium.org

Committed: https://code.google.com/p/gyp/source/detail?r=1972

[sky, 2014-09-02 21:59:59]

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

[scottmg, 2014-09-02 22:06:45]

lgtm

https://codereview.chromium.org/534793002/diff/1/pylib/gyp/generator/analyzer.py
File pylib/gyp/generator/analyzer.py (right):

https://codereview.chromium.org/534793002/diff/1/pylib/gyp/generator/analyzer...
pylib/gyp/generator/analyzer.py:135: if path.startswith(toplevel_dir + '/'):
will there be any problems with \ here?

[sky, 2014-09-02 22:11:30]

https://codereview.chromium.org/534793002/diff/1/pylib/gyp/generator/analyzer.py
File pylib/gyp/generator/analyzer.py (right):

https://codereview.chromium.org/534793002/diff/1/pylib/gyp/generator/analyzer...
pylib/gyp/generator/analyzer.py:135: if path.startswith(toplevel_dir + '/'):
On 2014/09/02 22:06:45, scottmg wrote:
> will there be any problems with \ here?

Paths should have been mapped to / by the time we get here.

[sky, 2014-09-02 22:12:03]

Committed patchset #1 (id:1) manually as r1972 (presubmit successful).