-
Notifications
You must be signed in to change notification settings - Fork 304
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
Separate MG library from SG library #1770
Labels
? - Needs Triage
Need team to review and classify
Epic
Tracker for a relatively large body of work that is broken down into stories and issues
Comments
ChuckHastings
added
2 - In Progress
feature request
New feature or request
and removed
? - Needs Triage
Need team to review and classify
labels
Aug 12, 2021
rapids-bot bot
pushed a commit
that referenced
this issue
Sep 8, 2021
Partially addresses #1770 This is preliminary work to separate the SG and MG shared object libraries. This PR splits many of the source files that instantiate SG and MG variants of algorithms/objects/functions. There will be subsequent PRs that will refactor the CMake structure and probably move some more files around. Authors: - Chuck Hastings (https://github.com/ChuckHastings) Approvers: - Seunghwa Kang (https://github.com/seunghwak) URL: #1803
ChuckHastings
added
the
Epic
Tracker for a relatively large body of work that is broken down into stories and issues
label
Nov 15, 2021
ChuckHastings
changed the title
[ENH] Separate MG library from SG library
[EPIC] Separate MG library from SG library
Nov 15, 2021
kingmesal
changed the title
[EPIC] Separate MG library from SG library
Separate MG library from SG library
Feb 14, 2023
closing due to no longer needing this feature. PLC handles most of the reasons we would need a non-MG package. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
? - Needs Triage
Need team to review and classify
Epic
Tracker for a relatively large body of work that is broken down into stories and issues
We have several issues regarding MG development:
We expect there will continue to be many users that will want to use SG cugraph analytics and won't need the MG capabilities.
To that end, this issue intends to separate the MG library into a separate shared object library. This will allow SG users to use just the SG library and its dependencies. An MG user will also build/download the MG library (along with its dependencies).
This effort will need to be followed up by one or more packaging efforts (e.g. making separate Conda packages) to truly expose this to the user.
Tasks
The text was updated successfully, but these errors were encountered: