Hardcoded assumption on LLVM directory name breaks external LLVM build support
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 624
- Forks
- 170
- PR merge metrics
- No merged PRs in 30d
Description
At
https://github.com/wsmoses/Polygeist/blob/2e6bb368ff4894993eb2102c1da3389fa18e49ef/CMakeLists.txt#L22
an assumption is made on the name of the directory wherein LLVM is being built. This seems to be hardcoded for the unified build. In turn, this breaks whenever llvm is not build inside a directory called llvm-project
Contributor guide
No contributing guide indexed for this repository
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 CMakeLists.txt line 22 and inspect how the unified build derives the LLVM build directory. Verify the configuration with an external LLVM build whose directory is not named llvm-project; done means Polygeist configures without assuming that directory name.
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
- Mostly clear
- Newbie friendliness
- 42/100