Make sure Chromoting GN header checks are enabled and passing |
||||
Issue descriptionGN has a feature to verify includes to make sure the corresponding dependencies are present in the build rules. There is a white list to specify what parts of the tree should have this check run. We should make sure we are included in the whitelist and address any errors that may be uncovered as a result.
,
Jan 29 2018
Returning this to Untriaged. I hit an issue with this today; will upload one or two CLs to get at least some GN check coverage working. :)
,
Feb 12 2018
https://chromium-review.googlesource.com/c/chromium/src/+/910730 as a workaround for the implicit //base dependencies, FWIW.
,
Feb 12 2018
https://chromium-review.googlesource.com/c/chromium/src/+/910730 as a workaround for the implicit //base dependencies, FWIW.
,
May 15 2018
No activity for a while, so it doesn't seem important.
,
May 15 2018
Actually there have been several patch-ups to the BUILD.gn files since I filed this, each fixing individual specific instances of build breakage, without actually getting GN check working (e.g. when a new generated header was added to //base). |
||||
►
Sign in to add a comment |
||||
Comment 1 by sergeyu@chromium.org
, Mar 31 2016