microsoft / microsoft/DirectXShaderCompiler
Use VCPKG manifest mode for directx-headers instead of a submodule
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C++
- Stars
- 3.7k
- Forks
- 900
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 44
Description
The repo uses submodules which makes it very hard to use this repo in VCPKG.
Why not use VCPKG manifest mode for directx-headers instead of a submodule? There is also a spirv-tools port as well, and you can easily add one for the spriv-headers as well.
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 locating the repository's submodule configuration and any existing VCPKG integration. Compare how directx-headers and spirv-tools are currently brought in, then determine the manifest entries needed for directx-headers and spriv-headers and verify that the normal build still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100