test: stop building tons of copies of gtest/gmock objects

test: stop building tons of copies of gtest/gmock objects

The current makefile ends up building ~17 copies of the gtest/gmock
objects -- every test that refers to the cc files directly will have
its own copy.  This is because the build doesn't know if CFLAGS and
such have changed between each target (and in some cases, they are).

Create a new libtesting.a target to hold a single copy of these files
and update all of the unittests to link that in.  This speeds up the
build a bit especially when you aren't using ccache.

This does mean we can no longer build gtest/gmock with unique flags,
but we haven't wanted that so far, so clearly no one wants that.

BUG=chromium:579384
TEST=`make check` passes
R=thestig@chromium.org

Committed: https://chromium.googlesource.com/breakpad/breakpad/+/83f0e6a31cd7e86e36a2a33085e86f8cc2a6fa7b

[vapier, 2016-01-25 21:59:20]

vapier@chromium.org changed reviewers:
+ mark@chromium.org, thestig@chromium.org

[Lei Zhang, 2016-01-25 22:26:16]

lgtm

[vapier, 2016-01-25 22:41:57]

Description was changed from

==========
test: stop building tons of copies of gtest/gmock objects

The current makefile ends up building ~17 copies of the gtest/gmock
objects -- every test that refers to the cc files directly will have
its own copy.  This is because the build doesn't know if CFLAGS and
such have changed between each target (and in some cases, they are).

Create a new libtesting.a target to hold a single copy of these files
and update all of the unittests to link that in.  This speeds up the
build a bit especially when you aren't using ccache.

This does mean we can no longer build gtest/gmock with unique flags,
but we haven't wanted that so far, so clearly no one wants that.

BUG=chromium:579384
TEST=`make check` passes
==========

to

==========
test: stop building tons of copies of gtest/gmock objects

The current makefile ends up building ~17 copies of the gtest/gmock
objects -- every test that refers to the cc files directly will have
its own copy.  This is because the build doesn't know if CFLAGS and
such have changed between each target (and in some cases, they are).

Create a new libtesting.a target to hold a single copy of these files
and update all of the unittests to link that in.  This speeds up the
build a bit especially when you aren't using ccache.

This does mean we can no longer build gtest/gmock with unique flags,
but we haven't wanted that so far, so clearly no one wants that.

BUG=chromium:579384
TEST=`make check` passes
R=thestig@chromium.org

Committed:
https://chromium.googlesource.com/breakpad/breakpad/+/83f0e6a31cd7e86e36a2a33...
==========

[vapier, 2016-01-25 22:41:58]

Committed patchset #1 (id:1) manually as
83f0e6a31cd7e86e36a2a33085e86f8cc2a6fa7b (presubmit successful).