Bug: skia:9756 In CanvasKit, a large part of the binary is for encoding. Clients would be happier with a smaller binary and no webp/jpeg encoding. Make this an option by splitting up the GN arguments. Split SK_HAS_WEBP_LIBRARY into SK_CODEC_DECODES_WEBP (to match the existing SK_CODEC_DECODES_RAW) and SK_ENCODE_WEBP. Same for JPEG and PNG. Update CanvasKit compile script to disable webp and jpeg encoding. Update debugger compile script to disable all encoding. Change IsPng signature to match other SkCodecs. Change-Id: Iec8466ee1b76bc3d1e377c24201068b776cd7718 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/273768 Commit-Queue: Leon Scroggins <scroggo@google.com> Reviewed-by: Derek Sollenberger <djsollen@google.com> Reviewed-by: Kevin Lubick <kjlubick@google.com> Reviewed-by: Nathaniel Nifong <nifong@google.com> |
||
---|---|---|
.. | ||
build | ||
builder_name_schema | ||
checkout | ||
docker | ||
doxygen | ||
env | ||
flavor | ||
git | ||
gsutil | ||
infra | ||
run | ||
vars | ||
README.md |
Skia Recipe Modules
This directory contains recipe modules designed to be used by recipes (see infra/bots/recipes). They are all Skia-specific and some are interrelated:
- builder_name_schema - Helps to derive expected behavior from task (formerly builder) names.
- core - Use as a starting point for most recipes: runs setup and sync steps.
- ct - Shared Cluster Telemetry utilities.
- flavor - Allows the caller to specify a high-level command to run, leaving the platform-specific details to be handled by the specific flavor module.
- infra - Shared infrastructure-related utilities.
- run - Utilities for running commands.
- swarming - Utilities for running Swarming tasks.
- vars - Common global variables used by Skia recipes/modules.
When you change a recipe module, you generally need to re-train the simulation test:
$ python infra/bots/recipes.py test run --train
Or:
$ cd infra/bots; make train
Each recipe module contains a few files:
- api.py - This is the meat of the module.
- __init__.py - Contains a single DEPS variable, indicating the other recipe modules on which this module depends.
- example.py - Optional, this file contains examples which demonstrate how to use the module and should contain enough tests to achieve 100% coverage for the module. The tests are run using the recipes test command above.