summaryrefslogtreecommitdiffstats
path: root/components
diff options
context:
space:
mode:
authorscottmg@chromium.org <scottmg@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-12-11 22:08:48 +0000
committerscottmg@chromium.org <scottmg@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-12-11 22:08:48 +0000
commitc1a2b233574df6256681b1ed1f7a18a10d942d10 (patch)
treeaddef502fc26d68815f4dc6add3b629d38d7ee5d /components
parent559eec21d4f7a4a15d927176c2c49977eb111b97 (diff)
downloadchromium_src-c1a2b233574df6256681b1ed1f7a18a10d942d10.zip
chromium_src-c1a2b233574df6256681b1ed1f7a18a10d942d10.tar.gz
chromium_src-c1a2b233574df6256681b1ed1f7a18a10d942d10.tar.bz2
Move cloud_print manifestdependency to external .manifest file
I plan (https://codereview.chromium.org/111373002/) to make manifest handling simpler in gyp. In particular, doing the manifest embedding in one pass to avoid the need to invoke the linker twice. In order to do this /manifestdependency on the linker command line needs to be removed as it creates dependencies that are only made clear by having the linker generate a manifest. In this case it's simple enough to simply use a .manifest file with the same dependency information that can be merged beforehand. So, move from .gyp linker flags to a file in AdditionalManifestFiles. R=vitalybuka@chromium.org BUG=324863 Review URL: https://codereview.chromium.org/108813005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@240189 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'components')
0 files changed, 0 insertions, 0 deletions