• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

include/H12-Nov-2020-446328

source/H12-Nov-2020-563,336451,737

BUILD.gnH A D07-Nov-202011.7 KiB406372

DEPSH A D07-Nov-202080 87

OWNERSH A D07-Nov-2020119 65

README.chromiumH A D07-Nov-20201.2 KiB5035

generate_gni.shH A D07-Nov-202018.5 KiB527373

libvpx_srcs.gniH A D07-Nov-2020282.4 KiB4,4144,412

lint_config.shH A D07-Nov-20203 KiB11361

run_perl.pyH A D07-Nov-2020882 2916

README.chromium

1Name: libvpx
2URL: http://www.webmproject.org
3Version: v1.8.2
4CPEPrefix: cpe:/a:john_koleszar:libvpx:1.8.2
5License: BSD
6License File: source/libvpx/LICENSE
7Security Critical: yes
8
9Date: Tuesday March 31 2020
10Branch: master
11Commit: 667138e1f0581772de2b990e144bcd6c49a6adb8
12
13Description:
14Contains the sources used to compile libvpx binaries used by Google Chrome and
15Chromium.
16
17The libvpx source is from webmproject.org:
18  http://www.webmproject.org/code/
19  https://chromium.googlesource.com/webm/libvpx
20
21Please follow these steps to update libvpx source code:
22
231. Update the code:
24     roll_dep.py \
25       -r <libvpx OWNER> \
26       --log-limit 20 \
27       --roll-to <libvpx hash> \
28       src/third_party/libvpx/source/libvpx
29
30   Use the generated commit message for the roll.
31
322. Generate .gni and config files.
33
34   cd third_party/libvpx
35   ./generate_gni.sh
36
373. Update 'Branch' in README.chromium if necessary.
38
39Tools needed to build libvpx:
40
41- generate_gni.sh
42
43Generate config and .gni files that contain the source list for each platform.
44Configuration for the build is taken from vpx_config.h for each platform.
45
46- lint_config.sh
47
48A tool to verify vpx_config.h and vpx_config.asm are matched. This also
49prints the final configuration after checking.
50