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

Stop tagging wheels as arch-agnostic #507

Merged
merged 1 commit into from
Oct 23, 2024

Conversation

KyleFromNVIDIA
Copy link
Contributor

Since #479, the libkvikio wheel now includes platform-specific files. Stop tagging the wheel as "any".

Since rapidsai#479, the libkvikio
wheel now includes platform-specific files. Stop tagging the wheel
as "any".
@KyleFromNVIDIA KyleFromNVIDIA requested a review from a team as a code owner October 23, 2024 13:31
@KyleFromNVIDIA KyleFromNVIDIA requested a review from bdice October 23, 2024 13:31
@KyleFromNVIDIA KyleFromNVIDIA added bug Something isn't working non-breaking Introduces a non-breaking change labels Oct 23, 2024
@madsbk
Copy link
Member

madsbk commented Oct 23, 2024

/merge

@rapids-bot rapids-bot bot merged commit 7715e36 into rapidsai:branch-24.12 Oct 23, 2024
57 checks passed
@vyasr
Copy link
Contributor

vyasr commented Oct 23, 2024

Is this really what we want here? Should the libkvikio wheel actually contain libcurl builds, or should that all be set up as part of its interface so that something building against libkvikio will build curl? If the current build behavior is desirable, we should run auditwheel to get the wheels tagged as manylinux wheels. If the current behavior is not desirable, we need to update the build system so that libcurl is not built as part of the C++.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working non-breaking Introduces a non-breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants