README.chromium 1.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960
  1. Name: libvpx
  2. URL: https://chromium.googlesource.com/webm/libvpx
  3. Version: v1.12.0
  4. Date: Tuesday August 09 2022
  5. Revision: 8786aee5821801fe6b5a285be009ba67ea7f4e63
  6. CPEPrefix: cpe:/a:webmproject:libvpx:1.12.0
  7. License: BSD
  8. License File: source/libvpx/LICENSE
  9. Security Critical: yes
  10. Description:
  11. Contains the sources used to compile libvpx binaries used by Google Chrome and
  12. Chromium.
  13. The libvpx source is from webmproject.org:
  14. https://www.webmproject.org/code/
  15. Please follow these steps to update libvpx source code:
  16. 1. Update the code:
  17. roll_dep.py \
  18. -r <libvpx OWNER> \
  19. --log-limit 20 \
  20. --roll-to <libvpx hash> \
  21. src/third_party/libvpx/source/libvpx
  22. Use the generated commit message for the roll.
  23. 2. Generate .gni and config files.
  24. cd third_party/libvpx
  25. ./generate_gni.sh
  26. Update 'Version' and 'CPEPrefix' in this file if necessary.
  27. 3. Amend the commit created by the first step:
  28. git commit -a --amend
  29. 4. Upload the change to Gerrit:
  30. git cl upload
  31. Run tryjobs:
  32. git cl try
  33. 5. Send out for review when all tryjobs pass. Submit it when +1 is granted.
  34. Tools needed to build libvpx:
  35. - generate_gni.sh
  36. Generate config and .gni files that contain the source list for each platform.
  37. Configuration for the build is taken from vpx_config.h for each platform.
  38. - lint_config.sh
  39. A tool to verify vpx_config.h and vpx_config.asm are matched. This also
  40. prints the final configuration after checking.