• Shared

  • arm64

• Shared (ios Simulator)

  • x64
  • arm64

• Wrapper Library
• Native Assets Library - Linux
• Native Assets Library - Windows
• Native Assets Library - Android
• Native Assets Library - iOS
• Native Assets Library - Mac OSX

Having a full HTML5 canvas compatible API could be quite a big benefit for many others and alphaSkia has big potential for that.

• API similar to OffscreenCanvas for image creation and drawing. (only 2D context, maybe some features not supported initially if they bloat the lib or are not built into Skia already)
• FontFace for handling fonts.
• Additional APIs:
  • like image saving (alternative to toDataURL)
  • Accept types like FontFace as setter for fonts (not only CSS string encoded font descriptions)
  • Unloading of fonts.

• Static
  • x64
  • x86
  • arm64
• Shared
  • x64
  • x86
  • arm64

Create a Kotlin Multiplatform Library for alphaSkia to be used in Kotlin/JVM and Kotlin/Native.

• Static
  • x64
  • arm64
• Shared
  • x64
  • arm64

We want to test for all libraries on all platforms the correct rendering output.

The test we perform is the same on all stages: We generate an alphaTab music sheet via generated test code using the alphaSkia API and visually test it against platform specific reference files. (like the visual regression tests in alphaTab).

• Test the native shared libraries using a test executable linked against them.

  • Goal: ensure produced binaries are generally OK + ensure correct output for the platform
  • Tested variants: linux-x64-shared, macos-x64-shared, windows-x64-shared, linux-x86-shared, macos-x64-shared, windows-x86-shared

• Test the dotnet nuget packages by consuming the nupkgs from a local source.

  • Goal: ensure native libs are correctly consumed and loaded.
  • Tested variants: linux-x64, macos-x64, windows-x64, linux-x86

• Test the Java packages by consuming the maven packages from a local source.

  • Goal: ensure native libs are correctly consumed and loaded.
  • Tested variants: linux-x64, macos-x64, windows-x64, linux-x86

• Test the Node packages by consuming the NPM packages via file:xxx.tgz dependencies.

  • Goal: ensure native libs are correctly consumed and loaded and we have no Node-API compat issues.
  • Tested variants: linux-x64, macos-x64, windows-x64, linux-x86
  • Tested node versions: lts/* and latest

Potential considerations:

• We could compile tests for all linux archs and run the binary via QEMU.
• Via a MAUI DeviceTests(https://github.com/dotnet/maui/wiki/DeviceTests) we could test the rendering output on Android an iOS.

Consider adding builds for linux musl to support alpine environments

• Static
  • x64
  • x86
  • arm
  • arm64
• Shared
  • x64
  • x86
  • arm
  • arm64

• Static
  • x64
  • x86
  • arm
  • arm64
• Shared
  • x64
  • x86
  • arm
  • arm64

The Shared libs are currently quite big with multiple MBs. Potentially there are still a lot of Skia symbols inside which we don't need. We should evaluate possibilities to strip those symbols.

• Check some skia symbols we definitely do not use and find out if they are contained in the shared lib.
• Review dllexport and visibility annotations when compiling shared/static libs as a potential cause for symbols not to be removed.
• Check other compiler and linker flags related to DCE and symbols stripping.
• Check source lists of LibSkia and potentially make our own with less files and modules inside.

• Wrapper Library
• Native Assets Library - Linux
• Native Assets Library - Windows
• Native Assets Library - Android
• Native Assets Library - Mac OSX

• Wrapper Library
• Native Assets Library - Linux
• Native Assets Library - Windows
• Native Assets Library - Mac OSX

Multiple node versions?

First compile a static library for all platforms and then we base the shared libs on this one. Similar as we build the JNI libs based on the static ones we can do the same for the shared libs.

Then we can start using the pinvoke source generation.
https://learn.microsoft.com/en-us/dotnet/standard/native-interop/pinvoke-source-generation

• DotNet -> NuGet
• Java -> Maven
• Node -> NPM.js