Stop linking a static_initializer into the Mac chromium build.

The :angle-image_util target was a source_set rather than a static_library(), causing us to link in loadimage.cpp, which pulled in mathutils.cpp, which contains a static initializer. Switching :angle_image_util to a static library (which is what GYP does) solved the problem. R=rsesek@chromium.org, cwallez@chromium.org BUG=628052 Change-Id: I63387b3fc9d799c92f7c1b49a1c7c7435e70a951 Reviewed-on: https://chromium-review.googlesource.com/360228Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Reviewed-by: Dirk Pranke <dpranke@chromium.org>

Stop linking a static_initializer into the Mac chromium build.
313d9447 · Dirk Pranke · Corentin Wallez · 4c32feb1 · 313d9447
Commit 313d9447 authored Jul 13, 2016 by Dirk Pranke Committed by Corentin Wallez Jul 14, 2016
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

BUILD.gn BUILD.gn +1 -1

No files found.
--- a/BUILD.gn
+++ b/BUILD.gn
@@ -158,7 +158,7 @@ config("angle_image_util_config") {
  ]
 }
-source_set("angle_image_util") {
+static_library("angle_image_util") {
  sources = rebase_path(gles_gypi.libangle_image_util_sources, ".", "src")
  configs -= angle_undefine_configs