GN: visibility not respected for configs |
||||
Issue description
I would expect the following to report an error about incorrect visibility, but gn does seems to ignore the visibility for the config:
config("foo") {
visibility = [ ":bar" ]
include_dirs = [ "foo" ]
}
source_set("bar") {
configs += [ ":foo" ]
}
source_set("baz") {
configs += [ ":foo" ]
}
$ gn out/xxx
Done. Made 5010 targets from 958 files in 1270ms
Instead I would expect something like the following (that I get when I change "foo" to a source_set and configs to deps):
$ gn gen out/xxx
ERROR at //BUILD.gn:36:1: Dependency not allowed.
source_set("baz") {
^------------------
The item //:baz
can not depend on //:foo
because it is not in //:foo's visibility list: [
//.:bar
]
,
Aug 22 2017
,
Nov 10 2017
,
Nov 12
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 12
|
||||
►
Sign in to add a comment |
||||
Comment 1 by brettw@chromium.org
, Sep 6 2016