Investigate following DAG for targets for `cuda` and `cuda_runtime`
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 296
- Forks
- 66
- Avg merge
- 1h 3m
- Merged PRs (30d)
- 1
Description
We have logic in blt_add_library and blt_add_executable that searches the DEPENDS_ON list for our cuda targets. It would clean a lot of inheritance up if we searched the DAG as well. This would remove the requirement that users have to list cuda or cuda_runtime on every target.
A general macro to search the DAG for a given target would be very helpful as well. Something like:
blt_is_target_dependent(TARGET foo DEPENDENCY cuda OUT is_dependent)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the existing CUDA-target handling in blt_add_library and blt_add_executable, focusing on how their DEPENDS_ON lists are searched. Investigate the DAG traversal and the proposed blt_is_target_dependent macro; done should mean CUDA dependencies are found transitively and a reusable target-dependency check is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100