tree 09d04ee9930927af0fce35b227dbde4a37b2cfc7
parent 40668140e7539ee1ae3b14bf10b6513c158b5096
author László Csomor <laszlocsomor@google.com> 1488298472 +0000
committer Yue Gan <yueg@google.com> 1488301378 +0000

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 https://github.com/bazelbuild/bazel/issues/2157

--
Change-Id: Iec327febb882aeaabae55216d0d06488f7c151ed
Reviewed-on: https://cr.bazel.build/9068
PiperOrigin-RevId: 148770951
MOS_MIGRATED_REVID=148770951