commit | dc5d71e83c1ce2a689f4fecdd692f1032f390f4d | [log] [tgz] |
---|---|---|
author | Alan Viverette <alanv@google.com> | Tue Mar 06 10:22:48 2018 -0500 |
committer | Alan Viverette <alanv@google.com> | Tue Mar 06 10:22:48 2018 -0500 |
tree | 4ce4794b3decfda59abc9162c8d61f43363383ea | |
parent | fd1a1d431fb2c5fba29e26e5466ddffa3a5ff27c [diff] |
Pull artifacts from 28.0.0-alpha1 release Also adds more Git mappings, which is probably fine? Change-Id: I61e8379f1e4cf653ff4523dcc30a2e4a39c79cd8 Fixes: 74213452 Test: ./gradlew dist
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
If you intend to repeatedly make changes to Support Library and to wish to see the results in your app, and you don't want to have to repeatedly build them as separate Gradle projects, you can configure your app build to build Support Library too
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)?