Revert "Add a whitespace.txt file"

This reverts commit 6703fe287670abf0e3473230bd1cdd551ab4107f.

Reason for revert: Builders flipped, triggering first LUCI job

Original change's description:
> Add a whitespace.txt file
> 
> Bug: 869249
> Change-Id: Iab9eeade2427255ce167fb524b11e0e3f691a685
> Reviewed-on: https://chromium-review.googlesource.com/1161382
> Reviewed-by: Frank Barchard <fbarchard@chromium.org>
> Commit-Queue: Ryan Tseng <hinoka@chromium.org>
> Commit-Queue: Frank Barchard <fbarchard@chromium.org>

TBR=hinoka@chromium.org,fbarchard@chromium.org
No-Try: True

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 869249
Change-Id: I00a29051b8a1be048afe444cd7811b19c949fd85
Reviewed-on: https://chromium-review.googlesource.com/1167906
Reviewed-by: Ryan Tseng <hinoka@chromium.org>
1 file changed
tree: 63f8fab2df566d231e80d950094b1ce6e75b2127
  1. .clang-format
  2. .gitignore
  3. .gn
  4. .vpython
  5. AUTHORS
  6. Android.bp
  7. Android.mk
  8. BUILD.gn
  9. CM_linux_packages.cmake
  10. CMakeLists.txt
  11. DEPS
  12. LICENSE
  13. OWNERS
  14. PATENTS
  15. PRESUBMIT.py
  16. README.chromium
  17. README.md
  18. all.gyp
  19. build_overrides/
  20. cleanup_links.py
  21. codereview.settings
  22. docs/
  23. download_vs_toolchain.py
  24. gyp_libyuv
  25. gyp_libyuv.py
  26. include/
  27. infra/
  28. libyuv.gni
  29. libyuv.gyp
  30. libyuv.gypi
  31. libyuv_nacl.gyp
  32. libyuv_test.gyp
  33. linux.mk
  34. public.mk
  35. pylintrc
  36. source/
  37. tools_libyuv/
  38. unit_test/
  39. util/
  40. 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] 1 for instructions on how to get started developing.

You can also browse the [docs directory] 2 for more documentation.