[NOT FOR COMMIT] Added GN support for Android .AAR packaged libraries

build/config/android/unpack_aar.py

+#!/usr/bin/env python
+#
+# Copyright 2016 The Chromium Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+"""Upacks the contents of an Android AAR."""
+
+import os
+import sys
+import zipfile
+
+
+def main():
+  if len(sys.argv) != 3:
+    print 'Usage: %s <aar_file> <output_dir>' % sys.argv[0]
+    sys.exit(1)
+
+  aar_file = sys.argv[1]  # e.g. library.aar
+  output_dir = sys.argv[2]  # e.g. path/to/output
+
+  #library_filename = os.path.basename(output_file)
+  #library_in_jar = os.path.join(library_filename)
+
+  with zipfile.ZipFile(aar_file, 'r') as archive:
+    archive.extractall(output_dir)

[agrieve, 2016/06/16 02:00:04]

Probably a good idea to assert that the .aar has no unsupported entries in it
(proguard.txt, assets, libs, jni)

[agrieve, 2016/06/16 02:00:04]

nit: you don't need to extract res/, so probably should skip that directory.
build_utils.ExtractAll(filter=) can be used for this.

[agrieve, 2016/06/16 02:00:04]

Probably a good idea to shutil.rmtree() first so that old extractions are
removed first.

[agrieve, 2016/06/16 02:00:04]

do you need an os.makedirs() first?

[agrieve, 2016/06/16 02:00:04]

For extra extra bonus points, it might be useful to validate that the
AndroidManifest.xml has no entries that require manifest merging (maybe via a
cludgy contains check)? A quick look tells me this should probably be good
enough:

if not options.ignore_manifest_merging:
  assert '<application>' not in manifest_data
  assert '<uses-permission' not in manifest_data

Most have just <application /> and <uses-sdk>, which are safely ignored.

If this check ever fails, the user would be responsible for manually copying in
the manifest changes and then adding the --ignore-manifest-merging (or
implementing manifest merging)

+
+
+if __name__ == '__main__':
+  sys.exit(main())