Google Git
Sign in
fuchsia / third_party / libyuv / HEAD
commit917276084a49be726c90292ff0a6b0a3d571a6af[log] [tgz]
authorJordan <rop@google.com>Tue Jan 27 06:12:56 2026 +0000
committerlibyuv LUCI CQ <libyuv-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jan 28 00:04:45 2026 -0800
tree644f48f30b639c5af19bb9847623320c03b619c4
parentf95782d01c13ce524dff7adbfadb8d78baf1e85b [diff]
Set Update Mechanism: Manual

This CL sets the Update Mechanism to Manual in README files.

Bug: 445311061
Change-Id: I4df6c5815b85c04b047b39b4352ba43789702d26
Reviewed-on: https://chromium-review.googlesource.com/c/libyuv/libyuv/+/7512992
Reviewed-by: Mirko Bonadei <mbonadei@chromium.org>
Commit-Queue: Mirko Bonadei <mbonadei@chromium.org>
Reviewed-by: Frank Barchard <fbarchard@chromium.org>
Owners-Override: Jordan Brown <rop@google.com>
1 file changed
tree: 644f48f30b639c5af19bb9847623320c03b619c4
  1. build_overrides/
  2. docs/
  3. include/
  4. infra/
  5. riscv_script/
  6. source/
  7. tools_libyuv/
  8. unit_test/
  9. util/
  10. .clang-format
  11. .gitignore
  12. .gn
  13. .vpython3
  14. Android.bp
  15. Android.mk
  16. AUTHORS
  17. BUILD.gn
  18. CM_linux_packages.cmake
  19. CMakeLists.txt
  20. codereview.settings
  21. DEPS
  22. DIR_METADATA
  23. download_vs_toolchain.py
  24. libyuv.gni
  25. libyuv.gyp
  26. libyuv.gypi
  27. LICENSE
  28. linux.mk
  29. OWNERS
  30. PATENTS
  31. PRESUBMIT.py
  32. public.mk
  33. pylintrc
  34. README.chromium
  35. README.md
  36. winarm.mk
README.md

libyuv is an open source project that includes YUV scaling and conversion functionality.

  • Scale YUV to prepare content for compression, with point, bilinear or box filter.
  • Convert to YUV from webcam formats for compression.
  • Convert to RGB formats for rendering/effects.
  • Rotate by 90/180/270 degrees to adjust for mobile devices in portrait mode.
  • Optimized for SSSE3/AVX2 on x86/x64.
  • Optimized for Neon/SVE2/SME on Arm.
  • Optimized for MSA on Mips.
  • Optimized for RVV on RISC-V.

Development

See Getting started for instructions on how to get started developing.

You can also browse the docs directory for more documentation.