-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document / Example how to use external android dependency like: Appcompat-v7 #1428
Comments
Yes, this is all unfortunately under-documented, which we're working on. The the rules created for the SDK are available at |
Keeping this issue open because this is still under-documented. In case anyone sees this in the future, the current syntax for external dependencies from the Android SDK is documented in issue #1745. |
This was documented in c3c4f36. The docs are now live on https://bazel.build/versions/master/docs/be/workspace.html#android_sdk_repository. |
Seems the android_sdk_repository is no longer documented on that page and @android-sdk//:appcompat_v7 no longer works. What's the correct way to add support library dependencies now? |
The documentation has been moved to the Android rules page: |
They're available from maven.google.com as standard Maven artifacts. There's no need to pull them from the SDK anymore. |
Yeah, I started trying to get the Maven artifacts working but got stuck. See #3633. |
The Android documentation does not explain how to deals with external android dependency like: Appcompat-v7.
http://www.bazel.io/docs/tutorial/android-app.html
The example should also illustrate such common task.
The text was updated successfully, but these errors were encountered: