Google Git
Sign in
chromium / libyuv / libyuv.git / db5c9792473b211b718ae1fe4ec61ec3ccfe8c5c
commitdb5c9792473b211b718ae1fe4ec61ec3ccfe8c5c[log] [tgz]
authorOleh Prypin <oprypin@webrtc.org>Fri Jul 19 13:30:09 2019
committerCommit Bot <commit-bot@chromium.org>Fri Jul 19 14:42:00 2019
tree4d7cd3a24ae4c3f87e225b343c14369a9849535b
parent33b1c1a1b1938913176152f9c271632423d04ca5 [diff]
Roll chromium_revision 4476bd69d1..e02114c8fa

Roll all versions in the DEPS file to match WebRTC's file
https://webrtc.googlesource.com/src/+/1a49c1338830b222bc6b22b4e0690615bcd6fa52/DEPS

Change log: https://chromium.googlesource.com/chromium/src/+log/4476bd69d1..e02114c8fa

Bug: None
Change-Id: Id70ae5fbac30ab73f71b83d8a8637dca220e7d5c
Reviewed-on: https://chromium-review.googlesource.com/c/libyuv/libyuv/+/1709450
Commit-Queue: Mirko Bonadei <mbonadei@chromium.org>
Commit-Queue: Oleh Prypin <oprypin@chromium.org>
Reviewed-by: Mirko Bonadei <mbonadei@chromium.org>
1 file changed
tree: 4d7cd3a24ae4c3f87e225b343c14369a9849535b
  1. build_overrides/
  2. docs/
  3. include/
  4. source/
  5. tools_libyuv/
  6. unit_test/
  7. util/
  8. .clang-format
  9. .gitignore
  10. .gn
  11. .vpython
  12. Android.bp
  13. Android.mk
  14. AUTHORS
  15. BUILD.gn
  16. cleanup_links.py
  17. CM_linux_packages.cmake
  18. CMakeLists.txt
  19. codereview.settings
  20. DEPS
  21. download_vs_toolchain.py
  22. libyuv.gni
  23. LICENSE
  24. linux.mk
  25. OWNERS
  26. PATENTS
  27. PRESUBMIT.py
  28. public.mk
  29. pylintrc
  30. README.chromium
  31. README.md
  32. 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 on Arm.
  • Optimized for MSA on Mips.

Development

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

You can also browse the docs directory for more documentation.