This moves ownership of the SkSurface to ThreadedSurface::fWindowSurface.
When we pass a Message to the SurfaceThread, we will include a pointer to ThreadedSurface.fWindowSurface so we can call:
getCanvas() to draw the SkPicture
WindowSurface's constructor so it can hold the WindowContext made during the init
To reference WindowSurface in SurfaceThread, we need to make a header for Surface.cpp (added in this cl)
Change-Id: I8c67223eee301a1b6e0d05934e1f8597cf70bc64
Reviewed-on: https://skia-review.googlesource.com/c/skia/+/404918
Commit-Queue: Jorge Betancourt <jmbetancourt@google.com>
Reviewed-by: Florin Malita <fmalita@chromium.org>
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
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");
}
...
}
e3f8030494