Build target for Android WebView.

android_webview/lib/DEPS

Index: android_webview/lib/DEPS
diff --git a/android_webview/lib/DEPS b/android_webview/lib/DEPS
new file mode 100644
index 0000000000000000000000000000000000000000..d1d409a8f2479a7be2260b9ed25906044dc03353
--- /dev/null
+++ b/android_webview/lib/DEPS
@@ -0,0 +1,6 @@
+include_rules = [

[Jói, 2012/08/02 15:20:00]

Could you add the following to this DEPS file, and any others created under
android_webview, to help make sure us Browser Components folks are aware of
added dependencies and can help break them ASAP?

# Please add joi@ or erikwright@ as reviewers for any changes
# to DEPS files under android_webview/.

[Torne, 2012/08/03 10:31:36]

Done.

+  "+content/public",
+
+  # Temporary until we no longer inherit from ChromeMainDelegate
+  "!chrome/app/chrome_main_delegate.h"

[Jói, 2012/08/02 15:20:00]

I believe the plan was for all the temporary dependencies on Chrome to be in
android_webview/dll, and none in lib.  Did I misunderstand?

[Torne, 2012/08/03 10:31:36]

Sorry, I arrived at a different structure separately, you didn't misunderstand,
I just wasn't in that conversation. :)

I've discussed the names with joth, and the "dll" vs "lib" names don't seem
ideal; it looks like we want to go with the library main code to be in
"lib/main" (with "lib" allowing deps on chrome) and the normal webview
implementation code to be in "native" and "java" and "test" and so on. I've
shuffled the code slightly more in the next version to match, and I've added
more comments/explanation to DEPS here, and also add a DEPS in android_webview
itself, to make this clearer.

Using "lib" for this is briefly confusing to the people who heard the earlier
suggestion, but in the long term I think it makes more sense.

+]