NVIDIA / NVIDIA/cuvs

[FEA] Enable option in `build.sh` to build self-contained tarball

Open
#1,789 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
Cuda
Stars
854
Forks
236
Avg merge
3d 3h
Merged PRs (30d)
62

Description

We now have a script for CI to build a standalone tarball of cuvs here. However, this script assumes it's being run in a CI environment (complete with functions for rapids-logger and appropriate env vars set).

We would like to enable a simple way for users to build the tarballs themselves using a method like:

build.sh libcuvs --install build/libcuvs_c --rapids-static
tar czvf libcuvs_c.tar.gz build/libcuvs_c

Even better, if we could have a simple command like this:

build.sh standalone

Which could build libcuvs automatically, then construct the tarball and put it in the build/ directory.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with build.sh and trace the CI-only functions, rapids-logger calls, and required environment variables. Define the standalone entry point or option so it builds libcuvs, creates the self-contained tarball, and places it in build/; verify the documented command works outside CI.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
build-system, devops
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.