To fix the gn check errors (see logs attached)
we use an explicit dependency so far:
//chrome/browser/web_applications:web_applications
//chrome/browser/web_applications:web_applications_on_extensions
`gn check` fails due to unconditionally included dependencies due to a conditionally-applied library dependency, it is usually a bug. The fix has traditionally been something like
#if defined(USE_AURA)
#include "ui/aura/window.h" // nogncheck
#endif
But maybe `gn check` is getting smarter about this. E.g. if a dependency had to stay,
#if BUILDFLAG(ENABLE_EXTENSIONS)
#include ".. /web_app.h"
#endif
should fix the complaints from `gn check`
Since web_app _shouldn't_ have an extensions dependency, that might not be the right fix.
To avoid a mess to untangle later, one fix might be to add a header in the target you want to depend on that #includes web_app.h so there's some indirection.
Context:
https://chromium-review.googlesource.com/c/chromium/src/+/1128665/6/chrome/browser/ui/BUILD.gn#1732
|
Deleted:
gn_check_chromeos.log
4.9 KB
|
|
Deleted:
gn_check_linux.log
2.8 KB
|
Comment 1 by loyso@chromium.org
, Jul 16Status: Started (was: Available)