unbundle: add replace_gn_files.py and unbundled GN file for libxml

build/linux/unbundle/libxml.gn

Index: build/linux/unbundle/libxml.gn
diff --git a/build/linux/unbundle/libxml.gn b/build/linux/unbundle/libxml.gn
new file mode 100644
index 0000000000000000000000000000000000000000..c481bd3547bb2b268a26e4582f689e53b5514728
--- /dev/null
+++ b/build/linux/unbundle/libxml.gn
@@ -0,0 +1,18 @@
+# Copyright 2016 The Chromium Authors. All rights reserved.

[Lei Zhang, 2016/04/04 21:46:28]

You should cross-reference with build/linux/unbundle/libxml.gyp and vice versa,
like any other GYP <-> GN file.

[Paweł Hajdan Jr., 2016/04/05 13:22:56]

Is there a standard way to do this? I haven't seen a style guide entry about
this, and the codebase doesn't seem to be consistent about it.

FWIW, real libxml GN/GYP files don't seem to have such cross-references.

Furthermore, since build/linux/unbundle is *NOT* really part of "mainline"
chromium codebase, it's also not in scope for GYP->GN migration.

I don't see any real use for adding cross-references here, especially if the
request is so vague. I could put something if you give a very specific
suggestion how such patch/comment should look like.

+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+import("//build/config/linux/pkg_config.gni")
+
+pkg_config("system_libxml") {
+  packages = [ "libxml-2.0" ]
+}
+
+static_library("libxml") {
+  sources = [
+    "chromium/libxml_utils.cc",
+    "chromium/libxml_utils.h",
+  ]
+
+  public_configs = [ ":system_libxml" ]
+}