blob: 6093bfcbd549103fda46a948ced1abd7be801156 [file] [log] [blame]
Name: libvpx
URL: http://www.webmproject.org
Version: v1.6.0
License: BSD
License File: source/libvpx/LICENSE
Security Critical: yes
Date: Wednesday August 23 2017
Branch: master
Commit: 30c261b1ebe8f06d687cac5b3b442d51a7839d00
Description:
Contains the sources used to compile libvpx binaries used by Google Chrome and
Chromium.
The libvpx source is from webmproject.org:
http://www.webmproject.org/code/
https://chromium.googlesource.com/webm/libvpx
Please follow these steps to update libvpx source code:
1. Update the code:
roll_dep.py \
-r <libvpx OWNER> \
--log-limit 20 \
--roll-to <libvpx hash> \
src/third_party/libvpx/source/libvpx
Use the generated commit message for the roll.
2. Generate .gni and config files.
cd third_party/libvpx
./generate_gni.sh
3. Update 'Branch' in README.chromium if necessary.
Tools needed to build libvpx:
- generate_gni.sh
Generate config and .gni files that contain the source list for each platform.
Configuration for the build is taken from vpx_config.h for each platform.
- lint_config.sh
A tool to verify vpx_config.h and vpx_config.asm are matched. This also
prints the final configuration after checking.
OSZAR »