commit | 6b896e6a827f7357214aa309500585779afa6dc0 | [log] [tgz] |
---|---|---|
author | Treehugger Robot <[email protected]> | Sun Jul 22 19:23:54 2018 +0000 |
committer | Gerrit Code Review <[email protected]> | Sun Jul 22 19:23:54 2018 +0000 |
tree | 30b1f097694c4a53c7a6075334f7eba861911c35 | |
parent | a41bee7bfec0a9e4d6e518120856a2588b1da60b [diff] | |
parent | a8417544e408d9f23fbc2ae7143167dc6ed4eda9 [diff] |
Merge "Update README.md file to be more up to date with AndroidX." into androidx-master-dev
We are not currently accepting new modules.
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 androidx-master-dev
Now your repository is set to pull only what you need for building and running Androix libraries. Download the code (and grab a coffee while we pull down 3GB):
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 AndroidX library from command line:
cd path/to/checkout/frameworks/support/ ./gradlew createArchive
If you intend to repeatedly make changes to AndroidX Libraries 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 AndroidX Libraries too
Run FooBarTest
Run androidx.foobar
AndroidX libraries has a set of Android applications that exercise AndroidX 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)?