2a650cc795
Add a Surface abstraction to manage the canvas backing store (equivalent to SkSurface). This allows relieving Canvas of buffer management duties - we can now focus solely on rendering APIs at this level. At the moment, only a Bitmap-backed surface is implemented -- but other native surface types will be added. Also relocate native code to 'src'. Change-Id: I46738472536cf24524428dbd36969f2b99d251e3 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/395536 Reviewed-by: Jorge Betancourt <jmbetancourt@google.com> Commit-Queue: Florin Malita <fmalita@google.com>
40 lines
1.2 KiB
Plaintext
40 lines
1.2 KiB
Plaintext
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");
|
||
}
|
||
|
||
...
|
||
}
|
||
|