5e8f45faf1
This updates all our callsites in preparation for removing the #include "include/core/SkColorSpace.h" from SkImageInfo.h According to go/chrome-includes [1], this will save ~150MB (0.07%) from the compilation size. I think SkColorSpace is a big include because it loads the skcms header, which is big. The follow-on CL will remove that link, once clients have been updated as well. [1] https://commondatastorage.googleapis.com/chromium-browser-clang/chrome_includes_2022-03-31_124042.html#view=edges&filter=%5Ethird_party%2Fskia%2Finclude%2Fcore%2FSkImageInfo%5C.h%24&sort=asize&reverse=&includer=%5Ethird_party%2Fskia%2Finclude%2Fcore%2FSkImageInfo%5C.h%24&included=&limit=1000 Change-Id: I1b5ff491ac495317b0e5af3a2082b080d43697ae Bug: skia:13052 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/525639 Reviewed-by: Robert Phillips <robertphillips@google.com> Reviewed-by: Brian Salomon <bsalomon@google.com> Reviewed-by: Florin Malita <fmalita@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com> |
||
---|---|---|
.. | ||
src | ||
README |
AndroidKit is an AAR, or Android Library, that compiles Skia's native code,
JNI bindings, and Java wrapper classes into a shared library.
BUILDING
1) Through Android Studio
- Start a project by opening skia/platform_tools/android/apps with Android Studio.
- Ensure that you're local.properties file is filled out with paths to your
Skia out directories. It should look like this:
sdk.dir=[sdk file path]
depot_tools.dir=[depot tools file path]
x86.out.dir=[out file for x86]
x64.out.dir=[out file for x64]
arm64.out.dir=[out file for xarm64]
arm.out.dir=[out file for arm]
- Click on AndroidKit on the project tree, click Build in the toolbar, and select
" Make Module 'apps.androidkit' "
- The AAR will be under the build/outputs/aar directory.
2) Through the terminal
- Run: platform_tools/android/bin/android_build_app -C out/[out_dir] androidkit
- If it builds with no errors, you’ll find the AAR in the out directory you were building from
LOADING
Before using AndroidKit classes, client applications must explicitly load the native library.
This is usually accomplished via a static class initializer, e.g.
public class MyApp {
static {
System.loadLibrary("androidkit");
}
...
}