Marcel Hlopko
Marcel Hlopko
FWIW I think that's our best shot at having working coverage for Rust anytime soon. Took a super-quick look and the PR looks reasonable. Thanks for working on it @keith!
Oh good point, I was thinking about people at the Bazel team who would be able to fix it, not about where to file it properly. I'll re-file at bazelbuild/bazel....
Closing as recommended by @jskeet
Late is better than never. We changed includes handling and we will now add 3 include directories per single include (srcs, genfiles, binfiles). I don't plan to optimize this in...
I wrote a doc proposing unifying C++ actions with Args (what all other actions use): https://docs.google.com/document/d/11DDjHQfCY3I1kO7w0PusjCoaqmZUQQajd42HDS0F3dI/edit#heading=h.4nax2orizccp
We discussed this offline with @laszlocsomor, and he'll ping this issue once he's done with his investigations with his plan.
We plan to work on this in the first half of 2019. Definitely before Bazel 1.0 is released.
Oh I thought clang-ifso didn't make it into clang, and that they're still waiting for tapi. I'll look into it when I find a free moment. But once the tool...
Oh cool! How did you wire it into the Bazel C++ toolchain? Maybe you're running the tool in the compilation action, and we only need it for the shared library...
Aren't header maps solving this problem? We have an external contribution at https://github.com/bazelbuild/bazel/pull/3712. Could you take a look at it and comment if it will help your use case?