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
Product: WebKit
Classification: Unclassified
Component: WebKit Misc.
: 528+ (Nightly build)
: PC Mac OS X 10.5
: P2 Normal
Assigned To: Yaar Schnitman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-10-01 15:19 PDT by Yaar Schnitman
Modified: 2009-10-02 11:41 PDT (History)
4 users (show)

See Also:


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

Note You need to log in before you can comment on or make changes to this bug.
Description Yaar Schnitman 2009-10-01 15:19:56 PDT
We don't want to use gyp_chromium out of its original context.
Comment 1 Yaar Schnitman 2009-10-02 11:22:11 PDT
Created attachment 40535 [details]
patch ads gyp_webkit
Comment 2 Dimitri Glazkov (Google) 2009-10-02 11:28:12 PDT
Comment on attachment 40535 [details]
patch ads gyp_webkit

nice.
Comment 3 WebKit Commit Bot 2009-10-02 11:41:48 PDT
Comment on attachment 40535 [details]
patch ads gyp_webkit

Clearing flags on attachment: 40535

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