chromium: Unset -Werror in gypFlags.
Thanks to @jcumming for notifying me about this in #nixos: 03:47 < jack_c> aszlig: chromium builds with -Werror by default. 03:47 < jack_c> Putting: werror = ""; 03:48 < jack_c> into gypFlags fixes that.. ... 03:52 < jack_c> aszlig: agree -Werror is a good linting tool, but it should probably disabled for distribution. So, I guess it makes sense in our case, especially because different GCC versions will issue different warnings. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This commit is contained in:
parent
6fcc6816e7
commit
79b1f3069a
|
@ -145,6 +145,7 @@ in stdenv.mkDerivation rec {
|
|||
use_cups = cupsSupport;
|
||||
linux_sandbox_path="${libExecPath}/${packageName}_sandbox";
|
||||
linux_sandbox_chrome_path="${libExecPath}/${packageName}";
|
||||
werror = "";
|
||||
} // optionalAttrs proprietaryCodecs {
|
||||
# enable support for the H.264 codec
|
||||
proprietary_codecs = true;
|
||||
|
|
Loading…
Reference in New Issue