We tend to abuse the includes attribute of cc_library: https://docs.bazel.build/versions/master/be/c-cpp.html#cc_library.includes. Using includes impact all the dependent rules and we end up with compiler invocations with a huge number of include directives, which are hard to troubleshoot. We rely on the includes attribute because our include paths are not relative to the WORKSPACE root (https://docs.bazel.build/versions/master/bazel-and-cpp.html#include-paths), which is understandable since the project originally did not support Bazel as a build system. Since we should come up with a cleaner solution if possible.
We tend to abuse the
includesattribute ofcc_library: https://docs.bazel.build/versions/master/be/c-cpp.html#cc_library.includes. Usingincludesimpact all the dependent rules and we end up with compiler invocations with a huge number of include directives, which are hard to troubleshoot. We rely on theincludesattribute because our include paths are not relative to the WORKSPACE root (https://docs.bazel.build/versions/master/bazel-and-cpp.html#include-paths), which is understandable since the project originally did not support Bazel as a build system. Since we should come up with a cleaner solution if possible.