UXP - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Lines
*	Update libaom to rev b25610052a1398032320008d69b51d2da94f5928	trav90	2018-10-19	-576/+624
\|
*	[aom] No longer necessary to run lint_config.sh anymore	trav90	2018-10-19	-146/+4
\| \| \| \|	Upstream can now code generate the rtcd interface files directly from the aom_config.h header, so we no longer have to generate an intermediate file by running lint_config.sh. This also means we can remove the code for creating a temporary directory.
*	Add missing : to libaom moz.build	trav90	2018-10-19	-2/+2
\|
*	[aom] Fixup moz.build	trav90	2018-10-19	-19/+31
\|
*	Update aom to v1.0.0	trav90	2018-10-19	-43831/+24522
\| \| \| \|	Update aom to commit id d14c5bb4f336ef1842046089849dee4a301fbbf0.
*	Add support for SSE 4.2 to libaom moz.build	trav90	2018-10-19	-0/+2
\|
*	Add aom_version.h	trav90	2018-10-19	-0/+7
\|
*	Update generate_sources_mozbuild.sh	trav90	2018-10-19	-177/+13
\| \| \| \|	This changes generate_sources_mozbuild.sh to call generate_sources_mozbuild.py to generate sources.mozbuild and config files and removes the parts of the script that are no longer necessary.
*	Add generate_sources_mozbuild.py	trav90	2018-10-19	-0/+172
\| \| \| \|	This uses the cmakeparser to generate sources.mozbuild and the config files for each platform.
*	Add Python cmake parser	trav90	2018-10-19	-0/+468
\| \| \| \|	Unfortunately, upstream has removed the configure+make build system our import script relies on to generate code and moz.build files.
*	[av1] Fix build issues	trav90	2018-10-18	-14/+16
\| \| \| \| \| \| \| \| \| \| \| \| \|	This revision of libaom has some conflicts with our vendor script and build system. A number of new .asm files have the same basename as .c files, which our build system cannot handle. To work around this, I manually renamed the conflicting files in the filesystem and sources.mozbuild. Also add av1_convolve_scale_sse4.c to sources.mozbuild manually. This is needed by the build but for some reason isn't picked up by generate_sources_mozbuild.sh.
*	Update aom to commit id e87fb2378f01103d5d6e477a4ef6892dc714e614	trav90	2018-10-18	-2535/+5113
\|
*	Export aom_config.h	trav90	2018-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 f5bdeac22930ff4c6b219be49c843db35970b918	trav90	2018-10-18	-1992/+12352
\|
*	[aom] Remove unused option	trav90	2018-10-17	-3/+3
\|
*	[aom] Filter out CONFIG_EXT_PARTITION_TYPES	trav90	2018-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 upstream	trav90	2018-10-17	-2/+2
\|
*	[aom] Add x86-win32-gcc config	trav90	2018-10-17	-0/+2
\|
*	[av1] Clean up duplicate filenames check	trav90	2018-10-17	-8/+7
\|
*	Update aom to slightly newer commit ID	trav90	2018-10-17	-628/+16395
\|
*	[aom] Enable YASM	trav90	2018-10-15	-0/+2
\|
*	[aom] Remove 32-bit Mac OS build config	trav90	2018-10-15	-3/+0
\|
*	Generate build description for libaom	trav90	2018-10-15	-0/+15811
\|
*	Port the libvpx mozbuild generator to aom	trav90	2018-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/.