diff options
| author | yaar@chromium.org <yaar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-09-18 17:14:46 +0000 |
|---|---|---|
| committer | yaar@chromium.org <yaar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-09-18 17:14:46 +0000 |
| commit | 11246b5a8d079c1a1983b9c455a4b4d3107d3c80 (patch) | |
| tree | b3835e4070f0a30716176aea40099d6dfdf052c3 /PRESUBMIT.py | |
| parent | 6d60e9b60fd6f35aeae795baa197895227dff072 (diff) | |
| download | chromium_src-11246b5a8d079c1a1983b9c455a4b4d3107d3c80.zip chromium_src-11246b5a8d079c1a1983b9c455a4b4d3107d3c80.tar.gz chromium_src-11246b5a8d079c1a1983b9c455a4b4d3107d3c80.tar.bz2 | |
Upstreamings parts of webkit.gyp (step 1)
This is step 1 a multi-step process that is part of the webkit chromium port.
This step includes:
A. Refactoring the wtf, pcre & webcore targets into separate files javascriptcore.gypi and webcore.gyp, which would eventually move upstream.
B. Refactoring the feature_define variables into features.gypi, to allow two sets of feature defines - one for chromium port and one for chromium.
C. Refactoring the config target into config.gyp, since currently both javascriptcore and webcore target depend on it.
Next steps:
2. Eliminate config dependency.
3. Make features.gypi only override built-in variables that live upstream (so we don't have to maintain 2 parallel feature lists).
4. Really move webcore.gyp & javascriptcore.gyp to webkit.org
Review URL: http://codereview.chromium.org/212003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@26584 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'PRESUBMIT.py')
0 files changed, 0 insertions, 0 deletions