CUDA compilation flags
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 296
- Forks
- 66
- Avg merge
- 1h 3m
- Merged PRs (30d)
- 1
Description
Is there a special way to propagate defines? I am adding a library that depends on cuda, and nvcc is being invoked., but `-D PARALLEL` is not being passed to nvcc. Am I doing something incorrectly?
` blt_add_library(
NAME vtkh_par
SOURCES ${vtkh_sources} ${vtkh_par_sources}
HEADERS ${vtkh_par_headers} ${vtkh_headers}
DEPENDS_ON ${vtkh_thirdparty_libs} mpi icet)`
`blt_add_target_compile_flags(TO vtkh_par FLAGS "-D PARALLEL")`
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 by reproducing the shown blt_add_library and blt_add_target_compile_flags calls, then trace how BLT propagates target compile flags to CUDA compilation. Confirm the behavior by checking whether -D PARALLEL reaches nvcc; done means the define is passed when building vtkh_par.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100