summaryrefslogtreecommitdiffstats
path: root/media/libaom
Commit message (Collapse)AuthorAgeLines
* Export aom_config.htrav902018-10-18-0/+7
| | | | Recent changes made this a public header, so it needs to be available to callers like AOMDecoder.
* Update aom to commit id f5bdeac22930ff4c6b219be49c843db35970b918trav902018-10-18-1992/+12352
|
* [aom] Remove unused optiontrav902018-10-17-3/+3
|
* [aom] Filter out CONFIG_EXT_PARTITION_TYPEStrav902018-10-17-0/+3
| | | | | | aom_dsp_rtcd_defs.pl checks only whether this key is present in the config, not whether it is set to true or not. Our script sets CONFIG_FOO=no for disabled options, while the upstream build system omits them, resulting in extra symbol declarations the build will never define. Work around this by stripping the offending disabled config key if it is disabled.
* Make aom_config.asm match upstreamtrav902018-10-17-2/+2
|
* [aom] Add x86-win32-gcc configtrav902018-10-17-0/+2
|
* [av1] Clean up duplicate filenames checktrav902018-10-17-8/+7
|
* Update aom to slightly newer commit IDtrav902018-10-17-628/+16395
|
* [aom] Enable YASMtrav902018-10-15-0/+2
|
* [aom] Remove 32-bit Mac OS build configtrav902018-10-15-3/+0
|
* Generate build description for libaomtrav902018-10-15-0/+15811
|
* Port the libvpx mozbuild generator to aomtrav902018-10-15-0/+516
This is a port of the libvpx scripts, themselves a port of Chromium's scripts to generate an external build description using hooks in the upstream configure and make scripts. The libaom library is a fork of libvpx so we can use a similar approach. The upstream source is located in $(topsrc_dir)/third_party/aom but the build description and any patches are under the media directory with the other codecs, similar to how zlib works. Config files and headers generated by the upstream build system are also under $(topsrc_dir)/media/libaom/.