microsoft / microsoft/DirectXShaderCompiler
Install target installs lots of unnecessary LLVM outputs
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3.7k
- Forks
- 900
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 44
Description
At the moment running make install (or ninja install) installs heaps of clang and llvm build products. I would expect that only the dxc executable, dxc headers and dxc libraries would be built and installed, i.e. what is copied here: https://github.com/microsoft/DirectXShaderCompiler/blob/master/appveyor.yml
Currently the following files are installed: https://gist.github.com/6270e81dd239ccecf17e6bc4ed4f1c03
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 with the install behavior invoked by make install and ninja install, then compare it with the files copied in appveyor.yml. Use the linked gist as the current-output reference; done means installation is limited to the dxc executable, dxc headers, and dxc libraries, with both install commands checked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100