commit | bb78f3f64b73d247a6e154b3170b410e47f6d73d | [log] [tgz] |
---|---|---|
author | Aurimas Liutikas <aurimas@google.com> | Mon Jun 19 11:30:37 2017 -0700 |
committer | Aurimas Liutikas <aurimas@google.com> | Mon Jun 19 11:47:34 2017 -0700 |
tree | 73d9ec346c3aff6302601715e73892ee996a1483 | |
parent | 3d079d099a4426538d5f532f947771991c7c7703 [diff] |
Clean up init.gradle sdk setup. - Only set android.dir for full checkouts. - Do not set android.home as that resets default sdk location. We actually do not need to set it as it works without setting it. This fixes the issue of sdk getting reset as you switch between projects or start a brand new project. Test: Tried switching projects and building support library. Change-Id: If3bf4652743231de0452f04428c53887235f8b41
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)?