gn: Fix gn build so cloud_print_unittests doesn't fail.

gn: Fix gn build so cloud_print_unittests doesn't fail in debug static builds.

BUG=none

Committed: https://crrev.com/85ac931d6d6d8bb53a0e5e02a48be6de6256853b
Cr-Commit-Position: refs/heads/master@{#325478}

[Elliot Glaysher, 2015-04-14 23:27:46]

erg@chromium.org changed reviewers:
+ jam@chromium.org

[jam, 2015-04-15 17:12:16]

ok i looked into this a bit more since it seemed confusing that this file is
needed. it's only used by content_ipc_logging.cc when IPC_MESSAGE_LOG_ENABLED is
defined (which is done by ipc_message.h for debug builds). So it'd be incorrect
to make content/common depend on that ppapi target always, and it would be odd
to specify something in build.gn based on what's done in C++ code. that would
argue for making ipc_logging a build flag. then only when it's set would
content/common's build file depend on that ppapi target

[Elliot Glaysher, 2015-04-15 20:28:16]

Did what you sent me in im. ptal.

[jam, 2015-04-16 03:54:35]

lgtm

[jam, 2015-04-16 03:55:37]

On 2015/04/16 03:54:35, jam wrote:
> lgtm

(I updated the description to make it clear when this is broken)

[Elliot Glaysher, 2015-04-16 18:05:48]

The CQ bit was checked by erg@chromium.org

[commit-bot: I haz the power, 2015-04-16 18:06:09]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1088013002/20001

[commit-bot: I haz the power, 2015-04-16 18:21:04]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-04-16 18:21:58]

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