bazel-contrib / bazel-contrib/rules_cuda
Support implementation_deps on cuda_object and cuda_library and (transitive) rdc
Open
enhancement
- Dominant language
- Starlark
- Stars
- 122
- Forks
- 73
- Avg merge
- 7h 34m
- Merged PRs (30d)
- 7
Description
implementation_deps are an option with cc_library and allow you to add deps that don't propagage
https://bazel.build/reference/be/c-cpp#cc_library.implementation_deps
Contributor guide
Research direction
Start by reading the linked Bazel cc_library.implementation_deps documentation, then trace the definitions of cuda_object and cuda_library and how rdc dependencies are propagated. Done means both rules accept implementation_deps with the intended non-propagating behavior and rdc works transitively, with coverage for these cases if the repository has relevant tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100