crashpad_in_chromium set but not declared, triggering warning every build |
|||
Issue description
Since yesterday when you build Chromium (some rather default configuration) you get a warning:
ninja: Entering directory `/home/bratell/src/chromium/src/out/Default'
[1/1] Regenerating ninja files
WARNING at //.gn:68:26: Build argument has no effect.
crashpad_in_chromium = true
^---
The variable "crashpad_in_chromium" was set as a build argument
but never appeared in a declare_args() block in any buildfile.
To view all possible args, run "gn args --list <out_dir>"
The build continued as if that argument was unspecified.
---
My args.gn (if it matters) is:
is_debug=true
is_clang=true
enable_nacl=false
use_sysroot=false
is_component_build = true
use_jumbo_build = true
jumbo_file_merge_limit = 100
enable_ipc_fuzzer = false
Other build with almost opposite flags that also has the warning: https://logs.chromium.org/v/?s=chromium%2Fbb%2Fchromium.fyi%2FFuchsia%2F12120%2F%2B%2Frecipes%2Fsteps%2Fgenerate_build_files%2F0%2Fstdout
,
Dec 12 2017
Might be Linux only?
,
Dec 12 2017
Make that Linux+Fuchsia
,
Dec 12 2017
Fixed by https://chromium-review.googlesource.com/c/chromium/src/+/792606 but waiting on https://chromium-review.googlesource.com/c/821210/
,
Dec 12 2017
After https://chromium.googlesource.com/chromium/src/+/e6b4822d8f6d1fd1d13c1a816486cdd832be18be. |
|||
►
Sign in to add a comment |
|||
Comment 1 by brat...@opera.com
, Dec 12 2017