summaryrefslogtreecommitdiffstats
path: root/media/libaom/README_MCP
Commit message (Collapse)AuthorAgeLines
* Update libaom to commit ID 1e227d41f0616de9548a673a83a21ef990b62591trav902018-10-19-1/+1
|
* Update libaom to rev b25610052a1398032320008d69b51d2da94f5928trav902018-10-19-1/+1
|
* Update aom to v1.0.0trav902018-10-19-1/+1
| | | | Update aom to commit id d14c5bb4f336ef1842046089849dee4a301fbbf0.
* Update aom to commit id e87fb2378f01103d5d6e477a4ef6892dc714e614trav902018-10-18-1/+1
|
* Update aom to commit id f5bdeac22930ff4c6b219be49c843db35970b918trav902018-10-18-1/+1
|
* Update aom to slightly newer commit IDtrav902018-10-17-1/+1
|
* Generate build description for libaomtrav902018-10-15-0/+2
|
* Port the libvpx mozbuild generator to aomtrav902018-10-15-0/+11
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/.