Switch from build-time to run-time flags for Project Spitzer.

Switch from build-time to run-time flags for Project Spitzer.

Contributed by dalecurtis@chromium.org.

This puts the desktop media playback pipeline behind a runtime flag
for Android; previously this was a combination of build-time and
run-time flags to avoid introducing a binary size increase before
we were ready for experiments.

This change will result in a ~480kb apk size increase on Android that has been
approved via Chrome Eng Review and klobag@ from the Chrome for Android team.
http://crbug.com/570711 tracks this size increase and plans to reduce it in
the future.

It paves the way for unifying our playback stacks across platforms and brings
previously-missing features and improved security to Android playback. More
technical details can be found in the linked bug below and design doc:
https://goo.gl/qC3OuL

BUG=507834, 570711, 570762
TEST=builds with gn/gyp work with unified path.
TBR=grt@chromium.org,dpranke@chromium.org,liberato@chromium.org,creis@chromium.org

Committed: https://crrev.com/fa2d9d4704677627af5c703fc4c04717f5425e4a
Cr-Commit-Position: refs/heads/master@{#366208}

[xhwang, 2015-12-18 21:53:44]

xhwang@chromium.org changed reviewers:
+ creis@chromium.org, dalecurtis@chromium.org, liberato@chromium.org

[xhwang, 2015-12-18 21:53:44]

This is the rebase of https://chromiumcodereview.appspot.com/1530063002/. Sorry,
I can't upload a new PS to an issue that's owned by dalecurtis@.

[xhwang, 2015-12-18 21:54:22]

Description was changed from

==========
Switch from build-time to run-time flags for Project Spitzer.

This puts the desktop media playback pipeline behind a runtime flag
for Android; previously this was a combination of build-time and
run-time flags to avoid introducing a binary size increase before
we were ready for experiments.

This change will result in a ~480kb apk size increase on Android that has been
approved via Chrome Eng Review and klobag@ from the Chrome for Android team.
http://crbug.com/570711 tracks this size increase and plans to reduce it in
the future.

It paves the way for unifying our playback stacks across platforms and brings
previously-missing features and improved security to Android playback. More
technical details can be found in the linked bug below and design doc:
https://goo.gl/qC3OuL

BUG=507834, 570711, 570762
TEST=builds with gn/gyp work with unified path.
TBR=grt@chromium.org,dpranke@chromium.org
==========

to

==========
Switch from build-time to run-time flags for Project Spitzer.

This puts the desktop media playback pipeline behind a runtime flag
for Android; previously this was a combination of build-time and
run-time flags to avoid introducing a binary size increase before
we were ready for experiments.

This change will result in a ~480kb apk size increase on Android that has been
approved via Chrome Eng Review and klobag@ from the Chrome for Android team.
http://crbug.com/570711 tracks this size increase and plans to reduce it in
the future.

It paves the way for unifying our playback stacks across platforms and brings
previously-missing features and improved security to Android playback. More
technical details can be found in the linked bug below and design doc:
https://goo.gl/qC3OuL

BUG=507834, 570711, 570762
TEST=builds with gn/gyp work with unified path.
TBR=grt@chromium.org,dpranke@chromium.org,liberato@chromium.org,creis@chromiu...
==========

[xhwang, 2015-12-18 21:58:13]

Description was changed from

==========
Switch from build-time to run-time flags for Project Spitzer.

This puts the desktop media playback pipeline behind a runtime flag
for Android; previously this was a combination of build-time and
run-time flags to avoid introducing a binary size increase before
we were ready for experiments.

This change will result in a ~480kb apk size increase on Android that has been
approved via Chrome Eng Review and klobag@ from the Chrome for Android team.
http://crbug.com/570711 tracks this size increase and plans to reduce it in
the future.

It paves the way for unifying our playback stacks across platforms and brings
previously-missing features and improved security to Android playback. More
technical details can be found in the linked bug below and design doc:
https://goo.gl/qC3OuL

BUG=507834, 570711, 570762
TEST=builds with gn/gyp work with unified path.
TBR=grt@chromium.org,dpranke@chromium.org,liberato@chromium.org,creis@chromiu...
==========

to

==========
Switch from build-time to run-time flags for Project Spitzer.

Contributed by dalecurtis@chromium.org.

This puts the desktop media playback pipeline behind a runtime flag
for Android; previously this was a combination of build-time and
run-time flags to avoid introducing a binary size increase before
we were ready for experiments.

This change will result in a ~480kb apk size increase on Android that has been
approved via Chrome Eng Review and klobag@ from the Chrome for Android team.
http://crbug.com/570711 tracks this size increase and plans to reduce it in
the future.

It paves the way for unifying our playback stacks across platforms and brings
previously-missing features and improved security to Android playback. More
technical details can be found in the linked bug below and design doc:
https://goo.gl/qC3OuL

BUG=507834, 570711, 570762
TEST=builds with gn/gyp work with unified path.
TBR=grt@chromium.org,dpranke@chromium.org,liberato@chromium.org,creis@chromiu...
==========

[xhwang, 2015-12-18 22:00:14]

The CQ bit was checked by xhwang@chromium.org

[commit-bot: I haz the power, 2015-12-18 22:00:43]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1541513002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1541513002/1

[commit-bot: I haz the power, 2015-12-18 23:31:25]

Description was changed from

==========
Switch from build-time to run-time flags for Project Spitzer.

Contributed by dalecurtis@chromium.org.

This puts the desktop media playback pipeline behind a runtime flag
for Android; previously this was a combination of build-time and
run-time flags to avoid introducing a binary size increase before
we were ready for experiments.

This change will result in a ~480kb apk size increase on Android that has been
approved via Chrome Eng Review and klobag@ from the Chrome for Android team.
http://crbug.com/570711 tracks this size increase and plans to reduce it in
the future.

It paves the way for unifying our playback stacks across platforms and brings
previously-missing features and improved security to Android playback. More
technical details can be found in the linked bug below and design doc:
https://goo.gl/qC3OuL

BUG=507834, 570711, 570762
TEST=builds with gn/gyp work with unified path.
TBR=grt@chromium.org,dpranke@chromium.org,liberato@chromium.org,creis@chromiu...
==========

to

==========
Switch from build-time to run-time flags for Project Spitzer.

Contributed by dalecurtis@chromium.org.

This puts the desktop media playback pipeline behind a runtime flag
for Android; previously this was a combination of build-time and
run-time flags to avoid introducing a binary size increase before
we were ready for experiments.

This change will result in a ~480kb apk size increase on Android that has been
approved via Chrome Eng Review and klobag@ from the Chrome for Android team.
http://crbug.com/570711 tracks this size increase and plans to reduce it in
the future.

It paves the way for unifying our playback stacks across platforms and brings
previously-missing features and improved security to Android playback. More
technical details can be found in the linked bug below and design doc:
https://goo.gl/qC3OuL

BUG=507834, 570711, 570762
TEST=builds with gn/gyp work with unified path.
TBR=grt@chromium.org,dpranke@chromium.org,liberato@chromium.org,creis@chromiu...
==========

[commit-bot: I haz the power, 2015-12-18 23:31:26]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-12-18 23:32:19]

Description was changed from

==========
Switch from build-time to run-time flags for Project Spitzer.

Contributed by dalecurtis@chromium.org.

This puts the desktop media playback pipeline behind a runtime flag
for Android; previously this was a combination of build-time and
run-time flags to avoid introducing a binary size increase before
we were ready for experiments.

This change will result in a ~480kb apk size increase on Android that has been
approved via Chrome Eng Review and klobag@ from the Chrome for Android team.
http://crbug.com/570711 tracks this size increase and plans to reduce it in
the future.

It paves the way for unifying our playback stacks across platforms and brings
previously-missing features and improved security to Android playback. More
technical details can be found in the linked bug below and design doc:
https://goo.gl/qC3OuL

BUG=507834, 570711, 570762
TEST=builds with gn/gyp work with unified path.
TBR=grt@chromium.org,dpranke@chromium.org,liberato@chromium.org,creis@chromiu...
==========

to

==========
Switch from build-time to run-time flags for Project Spitzer.

Contributed by dalecurtis@chromium.org.

This puts the desktop media playback pipeline behind a runtime flag
for Android; previously this was a combination of build-time and
run-time flags to avoid introducing a binary size increase before
we were ready for experiments.

This change will result in a ~480kb apk size increase on Android that has been
approved via Chrome Eng Review and klobag@ from the Chrome for Android team.
http://crbug.com/570711 tracks this size increase and plans to reduce it in
the future.

It paves the way for unifying our playback stacks across platforms and brings
previously-missing features and improved security to Android playback. More
technical details can be found in the linked bug below and design doc:
https://goo.gl/qC3OuL

BUG=507834, 570711, 570762
TEST=builds with gn/gyp work with unified path.
TBR=grt@chromium.org,dpranke@chromium.org,liberato@chromium.org,creis@chromiu...

Committed: https://crrev.com/fa2d9d4704677627af5c703fc4c04717f5425e4a
Cr-Commit-Position: refs/heads/master@{#366208}
==========

[commit-bot: I haz the power, 2015-12-18 23:32:20]

Patchset 1 (id:??) landed as
https://crrev.com/fa2d9d4704677627af5c703fc4c04717f5425e4a
Cr-Commit-Position: refs/heads/master@{#366208}

[Dirk Pranke, 2015-12-19 19:52:34]

lgtm

[DaleCurtis, 2015-12-19 20:30:09]

Looks like there was an uncaught issue on the android x86 builders:
https://build.chromium.org/p/chromium.android/builders/Android%20x86%20Builde...

Fix in the CQ here:
https://codereview.chromium.org/1540713002/