Issue #1769 - Part 1 Follow-up: Tidy up moz.build for highway and libjxl

highway upstream added a new header file to be included in highway.h after
 0.15.0 it seems, so we have to account for that in moz.build.
Also brought back allowing compiler warnings for libjxl and highway.
 Apparently the equivalent of AllowCompilerWarnings() is a bool whose name
 is UPPERCASE and uses under_scores instead of CamelCase.
This commit is contained in:
Job Bautista 2022-06-20 21:44:59 +08:00 committed by roytam1
commit 00a5d64018
2 changed files with 7 additions and 0 deletions

View file

@ -30,6 +30,7 @@ EXPORTS.hwy += [
EXPORTS.hwy.ops += [
"/media/highway/src/hwy/ops/arm_neon-inl.h",
"/media/highway/src/hwy/ops/arm_sve-inl.h",
"/media/highway/src/hwy/ops/emu128-inl.h",
"/media/highway/src/hwy/ops/generic_ops-inl.h",
"/media/highway/src/hwy/ops/rvv-inl.h",
"/media/highway/src/hwy/ops/scalar-inl.h",
@ -42,3 +43,6 @@ EXPORTS.hwy.ops += [
]
FINAL_LIBRARY = "gkmedias"
# We allow warnings for third-party code that can be updated from upstream.
ALLOW_COMPILER_WARNINGS = True

View file

@ -131,6 +131,9 @@ EXPORTS.jxl += [
FINAL_LIBRARY = "gkmedias"
# We allow warnings for third-party code that can be updated from upstream.
ALLOW_COMPILER_WARNINGS = True
# Clang 5.0 has a compiler bug that prevents build in c++17
# See https://gitlab.com/wg1/jpeg-xl/-/issues/227
# This should be okay since we are using the C API.