Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish a conda package to conda-forge #2152

Open
Tracked by #2148
leofang opened this issue Jul 31, 2024 · 2 comments
Open
Tracked by #2148

Publish a conda package to conda-forge #2152

leofang opened this issue Jul 31, 2024 · 2 comments

Comments

@leofang
Copy link
Member

leofang commented Jul 31, 2024

No description provided.

@bdice
Copy link
Contributor

bdice commented Jul 31, 2024

We already have a cccl conda package. What relationship will exist between cccl and cuda-cooperative? Does one depend on another at build time/run time? Do we ship cuda-cooperative features as a part of cccl?

https://github.com/conda-forge/cccl-feedstock/blob/main/recipe/meta.yaml

@leofang
Copy link
Member Author

leofang commented Aug 1, 2024

cuda.cooperative is a Python module that offers callable CUB warp/block routines for Numba CUDA kernels (#1973). In this case, CCCL headers are a run-time dependency of cuda-cooperative.

Currently for the wheel build, we opt to keep a private copy of CCCL headers:

for proj_dir, header_dir in cccl_headers:
src_path = os.path.abspath(
os.path.join(cccl_path, proj_dir, header_dir))
dst_path = os.path.join(project_path, 'cuda', '_include', proj_dir)
if os.path.exists(dst_path):
shutil.rmtree(dst_path)
shutil.copytree(src_path, dst_path)

but for conda we probably can just depend on the cccl package (and not cuda-cccl, since the intention was to follow the trunk as closely as possible).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

2 participants