-
Notifications
You must be signed in to change notification settings - Fork 61
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
Updating cuCIM's build/CI infra to use scikit-build
, rapids-cmake
, whl
builds, etc.
#305
Comments
If cuCIM moves forward with this transition I would recommend also making use of rapids-cmake, which has a lot of the helper functions I wrote to simplify the process. |
This PR ( rapidsai/cudf#10919 ) making this change to cuDF could serve as a good example |
Maybe a simpler example case is this KvikIO PR ( rapidsai/kvikio#32 ) |
@jakirkham requested that I share additional info about wheel builds here: cuCIM builds wheels in a different way than most of RAPIDS. The guide for RAPIDS wheel builds says to remove versioneer and migrate to pyproject.toml. If migrating to a build system that is more similar to the rest of RAPIDS, cuCIM should remove its usage of versioneer. Another part of this migration would be to move from the current setup.py to pyproject.toml. |
Additional context on rapids-cmake: I noticed a lot of CMake dependencies that are duplicating pinnings and features that are handled by rapids-cmake. Examples of dependencies supplied by rapids-cmake: https://docs.rapids.ai/api/rapids-cmake/stable/api/#cpm-pre-configured-packages This includes:
|
scikit-build
, rapids-cmake
, whl
builds, etc.
A good chunk of this was done in recent PRs:
Going to close this out. Anything else can be raised in more focused issues |
Other RAPIDS libraries have been moving to scikit-build for Python packages, this integrates nicely with CMake and can simplify the build process (as well as making other package builds like wheels easier). Would be good to investigate doing the same for cuCIM
cc @vyasr (who has some experience here)
The text was updated successfully, but these errors were encountered: