[QST] Why always install package from GitHub when running cuvs/examples/build.sh?
Open
Nobody has claimed this yet.
question
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
What is your question?
When I first execute the cuvs/examples/build.sh, some packages are installed by CPM.cmake from GitHub. When I modify the source files in cuvs/examples/cpp/src, I try to execute build.sh to compile, but the packages still need to be added by CPM, which costs a lot of time. I want to know how to avoid installing packages repeatedly.
Thanks in advance.
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
Read cuvs/examples/build.sh and its CPM.cmake setup first, then inspect how repeated builds handle dependencies after edits in cuvs/examples/cpp/src. Done means documenting or confirming a way to avoid reinstalling the packages on subsequent builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp
- Domain
- build-system
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100