commit | 2d0f75424d03e9c54ff733aedda4382c49c27d36 | [log] [tgz] |
---|---|---|
author | Aurimas Liutikas <aurimas@google.com> | Thu Feb 09 16:19:53 2017 -0800 |
committer | Aurimas Liutikas <aurimas@google.com> | Mon Feb 13 12:49:57 2017 -0800 |
tree | b7296a7e478406fbbb83acc00795aeafe5a436f7 | |
parent | 0800a58729f5fdc6e399cbd299fbbc7442dbdb38 [diff] |
Clean up of support-v13 after minSdk 14 bump. 1. Deprecate one method in FragmentCompat 2. Rename all the inner classes to FooBarApiXXImpl to make it consistent with v4. 3. Inline all the calls from higher API levels since we no longer compile with different SDK versions. Usage of new APIs will be caught using lint and lint can deal with method calls inline. Bug: 32794064 Test: ./gradlew assemble Change-Id: Ia610ed582dc4f0076ca2da027fe12e339520efb5
We are not currently accepting new modules, features, or behavior changes.
NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.
Follow the “Downloading the Source” guide to install and set up repo
tool, but instead of running the listed repo
commands to initialize the repository, run the folowing:
repo init -u https://android.googlesource.com/platform/manifest -b ub-supportlib-master
Now your repository is set to pull only what you need for building and running support library. Download the code (and grab a coffee while we pull down 7GB):
repo sync -j8 -c
You will use this command to sync your checkout in the future - it’s similar to git fetch
Open path/to/checkout/frameworks/support/
in Android Studio. Now you're ready edit, run, and test!
If you get “Unregistered VCS root detected” click “Add root” to enable git integration for Android Studio.
If you see any warnings (red underlines) run Build > Clean Project
.
You can do most of your work from Android Studio, however you can also build the full support library from command line:
cd path/to/checkout/frameworks/support/ ./gradlew createArchive
Run FooBarTest
Run android.support.foobar
Support library has a set of Android applications that exercise support library code. These applications can be useful when you want to debug a real running application, or reproduce a problem interactively, before writing test code.
These applications are named support-*-demos (e.g. support-4v-demos or support-leanback-demos. You can run them by clicking Run > Run ...
and choosing the desired application.
cd path/to/checkout/frameworks/support/ repo start my_branch_name . (make needed modifications) git commit -a repo upload --current-branch .
If you see the following prompt, choose always
:
Run hook scripts from https://android.googlesource.com/platform/manifest (yes/always/NO)?