RESOLVED FIXED 29986
chromium port should use its own gyp_xxx instead of gyp_chromium 
https://bugs.webkit.org/show_bug.cgi?id=29986
Summary chromium port should use its own gyp_xxx instead of gyp_chromium
Yaar Schnitman
Reported 2009-10-01 15:19:56 PDT
We don't want to use gyp_chromium out of its original context.
Attachments
patch ads gyp_webkit (4.85 KB, patch)
2009-10-02 11:22 PDT, Yaar Schnitman 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Yaar Schnitman
Comment 1 2009-10-02 11:22:11 PDT
Created attachment 40535 [details] patch ads gyp_webkit
Dimitri Glazkov (Google)
Comment 2 2009-10-02 11:28:12 PDT
Comment on attachment 40535 [details] patch ads gyp_webkit nice.
WebKit Commit Bot
Comment 3 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>
WebKit Commit Bot
Comment 4 2009-10-02 11:41:57 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.