IndexedDB: Fixed threading bugs with use of AtomicStrings.

Source/modules/BUILD.gn

Index: Source/modules/BUILD.gn
diff --git a/Source/modules/BUILD.gn b/Source/modules/BUILD.gn
index d3a3c987aee1de9b237ad921a4c089b282aba916..ea88a430a1ba427d77c3ffe65e5422bd8974970d 100644
--- a/Source/modules/BUILD.gn
+++ b/Source/modules/BUILD.gn
@@ -84,10 +84,29 @@ source_set("modules_testing") {
   ]
 }
 
-# GYP version: WebKit/Source/modules/modules.gyp:make_modules_generated
+action("module_names") {
+  script = "../build/scripts/make_names.py"
+
+  module_names_in = "indexeddb/IndexedDBNames.in"
+  inputs = make_names_files + [ module_names_in ]
+
+  outputs = [
+    "$blink_modules_output_dir/IndexedDBNames.cpp",

[jsbell, 2014/08/12 18:46:12]

Should we generate into an indexeddb/ subdir, so that include paths elsewhere
are "modules/indexeddb/IndexedDBNames.h" ?

I don't think we do that for other generated code (e.g. for events and bindings)
so probably *no*, but wanted to raise it as an option.

[cmumford, 2014/08/12 19:30:41]

Good question - I had the same thought and nearly asked you the same question.
We don't do it for other auto-generated code, but it would be more symmetrical
if we did. The header includes do look a bit odd without an indexeddb subdir.

On 2014/08/12 18:46:12, jsbell wrote:

+    "$blink_modules_output_dir/IndexedDBNames.h",
+  ]
+
+  args = [
+    rebase_path(module_names_in, root_build_dir),
+    "--output_dir",
+    rebase_path(blink_modules_output_dir, root_build_dir),
+  ]
+}
+
+# GYP version: WebKit/Source/modules/modules_generated.gyp:make_modules_generated
 group("make_modules_generated") {
   deps = [
     "//third_party/WebKit/Source/core:core_event_interfaces",
     "//third_party/WebKit/Source/bindings/modules:bindings_modules_generated",
+    ":module_names",
   ]
 }