chromium: fix M124+ build by using the vendored libwebp
at least until we figure out how to use our libwebp again. Works around the following error in the configure phase (pretty quick to reproduce): ~~~ Running phase: configurePhase ERROR Unresolved dependencies. //third_party/libavif:libavif_enc(//build/toolchain/linux/unbundle:default) needs //third_party/libwebp:libwebp_sharpyuv(//build/toolchain/linux/unbundle:default) ~~~ The lib.optionals saves us from rebuilding < M124 (ungoogled-chromium at this HEAD and all of electron-source).
This commit is contained in:
parent
2dd80cf5d2
commit
d93b17c0d4
|
@ -102,7 +102,14 @@ let
|
|||
"flac"
|
||||
"libjpeg"
|
||||
"libpng"
|
||||
] ++ lib.optionals (!chromiumVersionAtLeast "124") [
|
||||
# Use the vendored libwebp for M124+ until we figure out how to solve:
|
||||
# Running phase: configurePhase
|
||||
# ERROR Unresolved dependencies.
|
||||
# //third_party/libavif:libavif_enc(//build/toolchain/linux/unbundle:default)
|
||||
# needs //third_party/libwebp:libwebp_sharpyuv(//build/toolchain/linux/unbundle:default)
|
||||
"libwebp"
|
||||
] ++ [
|
||||
"libxslt"
|
||||
# "opus"
|
||||
];
|
||||
|
|
Loading…
Reference in New Issue
Block a user