GYP generator for GN

tools/gn/secondary/build/config/BUILDCONFIG.gn

Index: tools/gn/secondary/build/config/BUILDCONFIG.gn
diff --git a/tools/gn/secondary/build/config/BUILDCONFIG.gn b/tools/gn/secondary/build/config/BUILDCONFIG.gn
index d2e609daca838ba764dfb49cba9a7cd630fc3583..8ee35473dcc4e01e1766a014fce836f931ff33b8 100644
--- a/tools/gn/secondary/build/config/BUILDCONFIG.gn
+++ b/tools/gn/secondary/build/config/BUILDCONFIG.gn
@@ -162,7 +162,7 @@ set_sources_assignment_filter(sources_assignment_filter)
 if (is_component_build) {
   component_mode = "shared_library"
 } else {
-  component_mode = "source_set"
+  component_mode = "static_library"

[scottmg, 2013/10/15 19:58:21]

is this necessary with the mapping in GypBinaryTargetWriter::WriteType?

[brettw, 2013/10/15 21:18:06]

I was concerned about the following case: The gn target depends on base
(component). In GYP base is a shared library and in GN its a source set.

If base is marked external and the gn target isn't, then we'll get a
gn-generated gn target depending on the gyp-generated base target. But since gn
thinks base is a source set, it will pull the files in directly and I think it
won't work.

So if we have GN->GYP dependencies, the component mode has to match between the
two builds.

 }
 
 toolkit_uses_gtk = is_linux