Reland #2 of Enable whitelist generation for official builds.

Reland #2 of Enable whitelist generation for official builds.

Previous: https://codereview.chromium.org/2241383004/

Currently, all resources are included in PAK files when Chrome is
built locally. Only official_buildbot.sh uses a resource whitelist. This CL
enables local builds to use resource whitelisting by setting the
enable_resource_whitelist_generation gn flag to true, or by building an
official build.

This will allow developers to more easily monitor the changes in APK size
for each commit they make.

However, a large amount of output is generated (_pragma is used to
create warnings to allow whitelisted resources to be listed), so for now
the whitelist will only be generated for official builds.

This change results in a ~1.5 mb difference when calculating the APK size with resource_sizes.py.

BUG=632385
Committed: https://crrev.com/c7e6104c8c2ed8080115e92ff3c6f9d748e7feae
Cr-Commit-Position: refs/heads/master@{#413794}

[estevenson, 2016-08-23 14:54:22]

estevenson@chromium.org changed reviewers:
+ agrieve@chromium.org, dpranke@chromium.org

[estevenson, 2016-08-23 14:54:22]

ptal, the last attempt failed because I didn't realize that a different shared
library extension is used when is_debug = false.

[estevenson, 2016-08-23 14:54:41]

The CQ bit was checked by estevenson@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-08-23 14:55:00]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[agrieve, 2016-08-23 14:58:02]

On 2016/08/23 14:54:22, estevenson wrote:
> ptal, the last attempt failed because I didn't realize that a different shared
> library extension is used when is_debug = false.

lgtm

[Dirk Pranke, 2016-08-23 15:29:02]

lgtm

[commit-bot: I haz the power, 2016-08-23 16:17:47]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-23 16:17:47]

Dry run: Try jobs failed on following builders:
  win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[estevenson, 2016-08-23 17:02:52]

The CQ bit was checked by estevenson@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-08-23 17:03:26]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-23 18:32:35]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-23 18:32:36]

Dry run: This issue passed the CQ dry run.

[estevenson, 2016-08-23 18:33:03]

The CQ bit was checked by estevenson@chromium.org

[commit-bot: I haz the power, 2016-08-23 18:33:54]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-23 18:40:01]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-08-23 18:42:47]

Description was changed from

==========
Reland #2 of Enable whitelist generation for official builds.

Previous: https://codereview.chromium.org/2241383004/

Currently, all resources are included in PAK files when Chrome is
built locally. Only official_buildbot.sh uses a resource whitelist. This CL
enables local builds to use resource whitelisting by setting the
enable_resource_whitelist_generation gn flag to true, or by building an
official build.

This will allow developers to more easily monitor the changes in APK size
for each commit they make.

However, a large amount of output is generated (_pragma is used to
create warnings to allow whitelisted resources to be listed), so for now
the whitelist will only be generated for official builds.

This change results in a ~1.5 mb difference when calculating the APK size with
resource_sizes.py.

BUG=632385
==========

to

==========
Reland #2 of Enable whitelist generation for official builds.

Previous: https://codereview.chromium.org/2241383004/

Currently, all resources are included in PAK files when Chrome is
built locally. Only official_buildbot.sh uses a resource whitelist. This CL
enables local builds to use resource whitelisting by setting the
enable_resource_whitelist_generation gn flag to true, or by building an
official build.

This will allow developers to more easily monitor the changes in APK size
for each commit they make.

However, a large amount of output is generated (_pragma is used to
create warnings to allow whitelisted resources to be listed), so for now
the whitelist will only be generated for official builds.

This change results in a ~1.5 mb difference when calculating the APK size with
resource_sizes.py.

BUG=632385

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

[commit-bot: I haz the power, 2016-08-23 18:42:48]

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

[pkotwicz, 2016-08-23 22:21:13]

A revert of this CL (patchset #2 id:20001) has been created in
https://codereview.chromium.org/2277523002/ by pkotwicz@chromium.org.

The reason for reverting is: Breaking perf try bot
https://build.chromium.org/p/tryserver.chromium.perf/builders/android_perf_bi....