conda-forge / conda-forge/llvmdev-feedstock
LLVM utilities
- Dominant language
- Shell
- Stars
- 12
- Forks
- 54
- Avg merge
- 4h 15m
- Merged PRs (30d)
- 3
Description
### Comment:
Hi I'm in the process of swapping out a from-source LLVM build with the llvmdev packages.
utilities (count, not, FileCheck etc) end up in a non default location [here](https://github.com/conda-forge/llvmdev-feedstock/blob/main/recipe/build.sh#L47) and that's caused some problems for us particularly with the cmake function `add_lit_testsuite` where FileCheck for example is a dependency that cannot otherwise be found. What's the rational with the current design?
Contributor guide
Research direction
Start with the linked recipe/build.sh location around line 47 and inspect how LLVM utilities such as FileCheck are installed. Then review CMake's add_lit_testsuite expectations; done means the current utility placement and the resulting discoverability problem have a documented resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, shell
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100