microsoft / microsoft/DirectXShaderCompiler
How can I build `dxil` and `dxcompiler` as a static library?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3.7k
- Forks
- 900
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 44
Description
I know that it would be best to leave them as DLLs so that a driver upgrade of Windows SDK update can upgrade and "fix" my compiler.
However I'm mostly targetting SPIR-V and running the compilation at runtime and I have a habit of static linking all my depdendencies into the Engine (even if the engine itself is a DLL).
Anyone tried this before? Especially on Windows?
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 reviewing the repository's C++ build configuration and the existing dxil and dxcompiler targets, with particular attention to Windows builds. Determine whether static-library output is supported and what changes or documented build steps would be required; done means a reproducible answer for building both components statically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100