Bug 29986 - chromium port should use its own gyp_xxx instead of gyp_chromium
: chromium port should use its own gyp_xxx instead of gyp_chromium
Status: RESOLVED FIXED
: WebKit
WebKit Misc.
: 528+ (Nightly build)
: PC Mac OS X 10.5
: P2 Normal
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2009-10-01 15:19 PST by
Modified: 2009-10-02 11:41 PST (History)


Attachments
patch ads gyp_webkit (4.85 KB, patch)
2009-10-02 11:22 PST, Yaar Schnitman
no flags Review Patch | Details | Formatted Diff | Diff


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2009-10-01 15:19:56 PST
We don't want to use gyp_chromium out of its original context.
------- Comment #1 From 2009-10-02 11:22:11 PST -------
Created an attachment (id=40535) [details]
patch ads gyp_webkit
------- Comment #2 From 2009-10-02 11:28:12 PST -------
(From update of attachment 40535 [details])
nice.
------- Comment #3 From 2009-10-02 11:41:48 PST -------
(From update of attachment 40535 [details])
Clearing flags on attachment: 40535

Committed r49032: <http://trac.webkit.org/changeset/49032>
------- Comment #4 From 2009-10-02 11:41:57 PST -------
All reviewed patches have been landed.  Closing bug.