commit | b9a762ccc2352e984a30c061894a343962b5c880 | [log] [tgz] |
---|---|---|
author | Gustav Sennton <gsennton@google.com> | Tue Apr 03 22:23:48 2018 +0100 |
committer | Gustav Sennton <gsennton@google.com> | Thu Apr 05 21:23:46 2018 +0100 |
tree | 6a8276a23098e7dd45a0dd618cee4f8f7b303589 | |
parent | ddfe3c05add543f4b02036bd608e4558d7d31d0d [diff] |
[WebView Support Library] avoid passing any state to chromium on init To support several versions of the WebView Support Library within the same app/process we need to ensure the support library glue (in chromium) doesn't hold any global state referencing the (app-side of the) support library. With this CL we remove the only current global reference to the support library: SupportLibraryInfo. The only information kept within that reference was a list of feature flags. Those feature flags will now live in individual callback objects instead, like WebViewClientCompat. Corresponding Chromium CL: http://crrev/c/995212 Bug: 77539415 Test: run androidx.webkit tests. Change-Id: I61e06fb0d50e29f181f9340838e4d6f17588dea5
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)?