Revert of replace COMPILE_ASSERT with static_assert in chrome/installer/

Revert of replace COMPILE_ASSERT with static_assert in chrome/installer/ (patchset #1 id:1 of https://codereview.chromium.org/821673004/)

Reason for revert:
Changes breaks internal signing infrastructure (static_assert not defined in environment somehow).

Maybe after the holidays, we can revisit!

Original issue's description:
> replace COMPILE_ASSERT with static_assert in chrome/installer/
>
> BUG=442514
>
> Committed: https://crrev.com/b4aadc32a7fd6d42ac3cc9adbb20a8ee4a267572
> Cr-Commit-Position: refs/heads/master@{#309684}

TBR=gab@chromium.org,mostynb@opera.com
NOTREECHECKS=true
NOTRY=true
BUG=442514
Committed: https://crrev.com/da9d12af3c9a29fdbf41af975c5bb93fdc7b8138
Cr-Commit-Position: refs/heads/master@{#309720}

[penny, 2014-12-29 20:30:54]

Created Revert of replace COMPILE_ASSERT with static_assert in chrome/installer/

[commit-bot: I haz the power, 2014-12-29 20:31:54]

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

[commit-bot: I haz the power, 2014-12-29 20:31:55]

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

[commit-bot: I haz the power, 2014-12-29 20:31:56]

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer,
_not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[penny, 2014-12-29 21:37:06]

pennymac@chromium.org changed reviewers:
+ matthewyuan@chromium.org

[matthewyuan, 2014-12-29 21:37:31]

On 2014/12/29 20:31:56, I haz the power (commit-bot) wrote:
> No LGTM from a valid reviewer yet. Only full committers are accepted.
> Even if an LGTM may have been provided, it was from a non-committer,
> _not_ a full super star committer.
> See http://www.chromium.org/getting-involved/become-a-committer
> Note that this has nothing to do with OWNERS files.

lgtm

[gab, 2014-12-29 21:44:52]

lgtm, CC grt: looks like we need to double check internal infrastructure support
for C++11.

[matthewyuan, 2014-12-29 21:46:50]

The CQ bit was checked by matthewyuan@chromium.org

[matthewyuan, 2014-12-29 21:47:00]

The CQ bit was unchecked by matthewyuan@chromium.org

[penny, 2014-12-29 21:47:26]

The CQ bit was checked by pennymac@chromium.org

[penny, 2014-12-29 21:47:44]

The CQ bit was unchecked by pennymac@chromium.org

[penny, 2014-12-29 21:48:33]

The CQ bit was checked by pennymac@chromium.org

[commit-bot: I haz the power, 2014-12-29 21:49:28]

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

[commit-bot: I haz the power, 2014-12-29 21:50:21]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2014-12-29 21:51:06]

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

[Mostyn Bramley-Moore, 2014-12-29 21:55:28]

A temporary option might be to add a local macro for chrome/installer/ rather
than for all of chromium.  I can take a look after the holidays.

[gab, 2014-12-30 14:31:26]

On 2014/12/29 21:55:28, Mostyn Bramley-Moore wrote:
> A temporary option might be to add a local macro for chrome/installer/ rather
> than for all of chromium.  I can take a look after the holidays.

Yea that'd make sense IMO.