diff options
| author | yaar@chromium.org <yaar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-09-17 23:22:47 +0000 |
|---|---|---|
| committer | yaar@chromium.org <yaar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-09-17 23:22:47 +0000 |
| commit | 637118fb52d4736b5ecef1253b4c879f5fdaf00e (patch) | |
| tree | e1184cf573de94e89850e4184787e69f64e415f1 /net/flip/flip_frame_builder.cc | |
| parent | 2dcad8d696d69ec6e105b3d312162ad9aea3bbae (diff) | |
| download | chromium_src-637118fb52d4736b5ecef1253b4c879f5fdaf00e.zip chromium_src-637118fb52d4736b5ecef1253b4c879f5fdaf00e.tar.gz chromium_src-637118fb52d4736b5ecef1253b4c879f5fdaf00e.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@26523 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/flip/flip_frame_builder.cc')
0 files changed, 0 insertions, 0 deletions