zstd: switch from git submodule to system installed library and cmake FetchContent
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 5k
- Forks
- 622
- Avg merge
- 8h 37m
- Merged PRs (30d)
- 5
Description
People building SPTAG packages on Linux distributions will want to use the system installed zstd library. People building SPTAG in other situations will want to use the latest release of zstd. Using a git submodule means that builders are always locked into the version of zstd that you have chosen. If you switch to a system where you use system build dependencies or cmake FetchContent, then builders will be able to use the version of zstd that they choose.
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
No files or tests are named. Start by locating the CMake configuration and the zstd git submodule, then inspect how dependencies are currently included. Done means Linux package builds can use a system zstd library while other builds can obtain zstd through CMake FetchContent, with both paths building successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100