Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(345)

Side by Side Diff: docs/google_play_services.md

Issue 2527953002: [gmscore] Add Google Play services documentation (Closed)
Patch Set: comments Created 4 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
(Empty)
1 # Google Play services in Chrome for Android
2
3 [TOC]
4
5 Google employee? See [go/chrome-gms](https://goto.google.com/chrome-gms) for
6 more info.
7
8 ## General setup
9
10 The Google Play services are a combination of [services][play_store] exposed on
11 Android devices and [libraries][dev_doc] to interact with them. Chrome relies
12 on them for critical features like Sign in, Feedback or Cast.
13
14 The standard way of adding the Google Play services as a dependency to a project
15 is to import it through the Android SDK manager as a Maven repository. That
16 repository contains multiple versions of the library split into separate APIs
17 (for example Cast, GCM, Android Pay, etc). To avoid downloading a lot of data we
18 don't need to build Chrome, android checkouts of Chromium download an archive
19 containing only the APIs we currently need in Chrome, and in a single version.
20
21 The up to date list of clients and version used can be seen in
22 [//build/android/play_services/config.json][config_json_rel_path].
23
24 **Note**: If you are working on a feature that requires different or more recent
25 APIs, you will need to locally download the Google Play services SDK repository.
26
27 The simplest way to download the latest SDK is to run:
28
29 ```
30 $CHROMIUM_SRC/build/android/play_services/update.py sdk
31 ```
32
33 Check out the help of that script for more info.
34
35 [play_store]: https://play.google.com/store/apps/details?id=com.google.android.g ms
36 [dev_doc]: https://developers.google.com/android/guides/overview
37 [config_json_rel_path]: ../build/android/play_services/config.json
38
39 ## Adding a dependency on new APIs
40
41 As explained above, the default checkout has access to only a specific set of
42 APIs during builds. If your CL depends on some APIs that are not included in the
43 build, you will need [file an issue][bug_link] to request an update of our
44 dependencies.
45
46 Not doing so could make the CL fail on the trybots and commit queue. Even if it
47 passes, it might fail on the internal bots and result in the CL getting
48 reverted, so please make sure the APIs are available to the bots before
49 submitting.
50
51 [bug_link]:https://bugs.chromium.org/p/chromium/issues/entry?labels=Restrict-Vie w-Google,pri-1,Hotlist-GooglePlayServices&owner=dgn@chromium.org&os=Android
OLDNEW
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698