I am using bazel and there's cuda code and c++ code in the repo. IIUC rules_cuda patches rules_cc and changes some settings. Such changes apply to all the cc targets, not only cuda targets after we run rules_cc_toolchains().
Is it possible to limit the impact only to cuda_library without touching cc targets? I am currently encountering an issue of --features=external_include_paths not working since it's missing in the cc toolchain patched by rules_cuda. More generally, it would be great if rules_cc can be purely some implementation detail of rules_cuda / cuda_library without anything "leaking" outside cuda targets.
Hi,
I am using bazel and there's cuda code and c++ code in the repo. IIUC rules_cuda patches rules_cc and changes some settings. Such changes apply to all the cc targets, not only cuda targets after we run rules_cc_toolchains().
Is it possible to limit the impact only to cuda_library without touching cc targets? I am currently encountering an issue of --features=external_include_paths not working since it's missing in the cc toolchain patched by rules_cuda. More generally, it would be great if rules_cc can be purely some implementation detail of rules_cuda / cuda_library without anything "leaking" outside cuda targets.