Open carlosgalvezp opened 1 year ago
Is the below discussion related to the above issue?
Bazel "strip_include_prefix" or "includes" attributes in cc_import rules suggested solution in this thread -
I would like to work on this after completing my pending PR.
I went on reading what strip_include_prefix is?
Hi! No, those links are related to cc_import, while I'm referring to cc_library in this ticket :)
Yes that bazel issue is about cc_import
but the workaround for that and with the cc_library
they used includes
instead of strip_include_prefix
. So, I found it a good starting point.
I am looking more into this. https://groups.google.com/g/bazel-discuss/c/pQLmBVNJGZ4?pli=1
So that when users import google-benchmark, the headers are included as "system headers", instead of regular headers.
If this is not done, compilers will throw warnings at google-benchmark code, which users have no way to act upon. Users should be able to choose a highly restrictive set of warnings without having to fix them in google-benchmark.
Note that this pattern is already applied in the googletest repo.