Closed nicolov closed 6 years ago
I agree this is not great.
I haven't figured out how to include these things in the toolchain without triggering a circular dependency. I'll keep thinking about the best way to automate it, though. Suggestions welcome!
Have a proposed fix for this in https://github.com/vsco/bazel-toolchains/pull/12.
LMK if it works for you.
Should be resolved now.
Hey there, thanks for the great work here.
I was wondering how to stop having to depend on
'@org_chromium_libcxx//:cxx',
and:cxxabi
in eachcc_library
rule. It seems pretty tiresome to me. Custom macros are an option, but I was wondering if there was a way to add it to the CROSSTOOL configuration instead.