Bazel client: make some libraries visible to ijar
Ijar will use Bazel's file handling logic so that
we don't have to maintain two implementations, and
don't have to copy this code to implement the
Windows/MSVC code path in
third_party/ijar/platform_utils.cc.
See
MOS_MIGRATED_REVID=148770951
# Description:
# C++ utility source for Bazel
+package_group(
+ name = "ijar",
+ packages = [
+ "//third_party/ijar/...",
+ ],
+)
cc_library(
name = "util",
@@ -41,6 +47,7 @@ cc_library(
"file_platform.h",
],
visibility = [
+ ":ijar",
"//src/test/cpp/util:__pkg__",
"//src/tools/singlejar:__pkg__",
],
@@ -63,7 +70,10 @@ cc_library(
"//conditions:default": ["errors_posix.cc"],
}),
hdrs = ["errors.h"],
- visibility = ["//src/main/cpp:__subpackages__"],
+ visibility = [
+ ":ijar",
+ "//src/main/cpp:__subpackages__",
+ ],
deps = [":port"],
)
