summaryrefslogtreecommitdiffstats
path: root/devtools/client/framework/ToolboxProcess.jsm
diff options
context:
space:
mode:
authortrav90 <travawine@palemoon.org>2018-10-15 21:44:18 -0500
committertrav90 <travawine@palemoon.org>2018-10-15 21:44:18 -0500
commit07c17b6b98ed32fcecff15c083ab0fd878de3cf0 (patch)
tree403ca55d2e61cf99e2140714ef3555ec51301b8b /devtools/client/framework/ToolboxProcess.jsm
parentb927e0d5caad3a7703829bdc1093bfc67ef3fb97 (diff)
downloadUXP-07c17b6b98ed32fcecff15c083ab0fd878de3cf0.tar
UXP-07c17b6b98ed32fcecff15c083ab0fd878de3cf0.tar.gz
UXP-07c17b6b98ed32fcecff15c083ab0fd878de3cf0.tar.lz
UXP-07c17b6b98ed32fcecff15c083ab0fd878de3cf0.tar.xz
UXP-07c17b6b98ed32fcecff15c083ab0fd878de3cf0.zip
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/.
Diffstat (limited to 'devtools/client/framework/ToolboxProcess.jsm')
0 files changed, 0 insertions, 0 deletions