Move GnomeKeyringLoader to components/os_crypt

chrome/browser/BUILD.gn

Index: chrome/browser/BUILD.gn
diff --git a/chrome/browser/BUILD.gn b/chrome/browser/BUILD.gn
index 5ce556531fb8dc7bccb31a573d56d978ea01d78b..95698a86703e8b8702ab90b33f341c6b63fddadc 100644
--- a/chrome/browser/BUILD.gn
+++ b/chrome/browser/BUILD.gn
@@ -18,9 +18,6 @@ if (is_android) {
 } else {
   import("//tools/grit/grit_rule.gni")
 }
-if (is_desktop_linux) {
-  import("//build/config/linux/pkg_config.gni")
-}
 
 additional_modules_list_file =
     "$root_gen_dir/chrome/browser/internal/additional_modules_list.txt"
@@ -49,25 +46,6 @@ if (is_win) {
   }
 }
 
-if (is_desktop_linux) {
-  # Gnome-keyring is normally dynamically loaded. The gnome_keyring config
-  # will set this up.
-  pkg_config("gnome_keyring") {
-    packages = [ "gnome-keyring-1" ]
-    defines = [ "USE_GNOME_KEYRING" ]
-    ignore_libs = true
-  }
-
-  # If you want to link gnome-keyring directly (use only for unit tests)
-  # ADDITIONALLY add this config on top of ":gnome_keyring". pkg-config is a
-  # bit slow, so prefer not to run it again. In practice, gnome-keyring's libs
-  # are just itself and common gnome ones we link already, so we can get away
-  # with additionally just coding the library name here.
-  config("gnome_keyring_direct") {
-    libs = [ "gnome-keyring" ]
-  }
-}
-
 # Use a static library here because many test binaries depend on this but don't
 # require many files from it. This makes linking more efficient.
 split_static_library("browser") {
@@ -591,7 +569,7 @@ split_static_library("browser") {
     sources += rebase_path(gypi_values.chrome_browser_gnome_keyring_sources,
                            ".",
                            "//chrome")
-    configs += [ ":gnome_keyring" ]
+    configs += [ "//components/os_crypt:gnome_keyring" ]
   }
   if (is_desktop_linux) {
     sources += rebase_path(gypi_values.chrome_browser_libsecret_sources,