8 commits

Author	SHA1	Message	Date
trav90	368651059a	Update libaom to commit ID 1e227d41f0616de9548a673a83a21ef990b62591	2019-02-16 00:17:46 +08:00
trav90	3d109dd4fc	Update libaom to rev b25610052a1398032320008d69b51d2da94f5928	2019-02-16 00:17:40 +08:00
trav90	48f6d2e034	Update aom to v1.0.0 ... Update aom to commit id d14c5bb4f336ef1842046089849dee4a301fbbf0.	2019-02-16 00:17:30 +08:00
trav90	992c6637e3	Update aom to commit id e87fb2378f01103d5d6e477a4ef6892dc714e614	2019-02-16 00:17:15 +08:00
trav90	2ab8fcbfd1	Update aom to commit id f5bdeac22930ff4c6b219be49c843db35970b918	2019-02-16 00:17:05 +08:00
trav90	76f1e6edca	Update aom to slightly newer commit ID	2019-02-16 00:16:50 +08:00
trav90	28c6a9062e	Generate build description for libaom	2019-02-16 00:16:30 +08:00
trav90	eb8cd130a8	Port the libvpx mozbuild generator to aom ... 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/.	2019-02-16 00:16:25 +08:00