Use a shorter include paths on Windows.

Use a shorter include paths on Windows.

We were hitting the MAXPATH limit on the build.webkit.org win bots.

BUG=webkit.org/b/74320


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=114686

[dglazkov, 2011-12-15 01:16:11]

lgtm

[M-A Ruel, 2011-12-15 01:19:37]

(I don't really mind, still lgtm)

(Sorry I missed it)

http://codereview.chromium.org/8930019/diff/1/webkit/support/setup_third_part...
File webkit/support/setup_third_party.py (right):

http://codereview.chromium.org/8930019/diff/1/webkit/support/setup_third_part...
webkit/support/setup_third_party.py:107: # Windows has a file path limit of 260
characters that we can hit when
Why not do the same on all platforms?

[tony, 2011-12-15 17:56:38]

On 2011/12/15 01:19:37, Marc-Antoine Ruel wrote:
>
http://codereview.chromium.org/8930019/diff/1/webkit/support/setup_third_part...
> File webkit/support/setup_third_party.py (right):
> 
>
http://codereview.chromium.org/8930019/diff/1/webkit/support/setup_third_part...
> webkit/support/setup_third_party.py:107: # Windows has a file path limit of
260
> characters that we can hit when
> Why not do the same on all platforms?

It would work on Windows and Mac because we generate files into
WebKit/Source/WebKit/chromium/{build,xcodebuild}, but on Linux, we generate
files into WebKit/out.  On Linux, we would need to prepend
../../../Source/WebKit/chromium/ to the include path.

[commit-bot: I haz the power, 2011-12-15 17:57:15]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/tony@chromium.org/8930019/1

[commit-bot: I haz the power, 2011-12-15 19:56:02]

Change committed as 114686