RESOLVED FIXED 88273
nrwt should look in 'out' for binaries on chromium win to support ninja
https://bugs.webkit.org/show_bug.cgi?id=88273
Summary nrwt should look in 'out' for binaries on chromium win to support ninja
Dirk Pranke
Reported 2012-06-04 17:55:25 PDT
nrwt should look in 'out' for binaries on chromium win to support ninja
Attachments
Patch (3.75 KB, patch)
2012-06-04 18:00 PDT, Dirk Pranke
no flags
Patch (20.52 KB, patch)
2012-06-06 17:18 PDT, Dirk Pranke
tony: review+
Dirk Pranke
Comment 1 2012-06-04 18:00:37 PDT
Tony Chang
Comment 2 2012-06-05 09:52:33 PDT
Comment on attachment 145670 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=145670&action=review > Tools/ChangeLog:3 > + nrwt should look in 'out' for binaries on chromium win to support ninja With this change, mac, linux, and win all look in 'out' (sometimes first, sometimes second). It would be nice if we pushed the out logic up into chromium.py.
Dirk Pranke
Comment 3 2012-06-05 13:06:43 PDT
(In reply to comment #2) > (From update of attachment 145670 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=145670&action=review > > > Tools/ChangeLog:3 > > + nrwt should look in 'out' for binaries on chromium win to support ninja > > With this change, mac, linux, and win all look in 'out' (sometimes first, sometimes second). It would be nice if we pushed the out logic up into chromium.py. This is a fair point. Each port uses different logic as well as different locations, but that's probably not a good thing. I'll see if I can unify them.
Dirk Pranke
Comment 4 2012-06-06 17:18:12 PDT
Dirk Pranke
Comment 5 2012-06-06 17:32:04 PDT
Note You need to log in before you can comment on or make changes to this bug.