-
Notifications
You must be signed in to change notification settings - Fork 195
[cuda_pathfinder] Initial version of find_nvidia_headers.py
for nvshmem
(Minimal Viable Product)
#661
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
base: main
Are you sure you want to change the base?
Conversation
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
/ok to test |
|
Just wondering what is the status for this PR? |
I still need to fix this up, after merging #723 a couple days ago. |
Is there some mechanism so that user can override the path returned by the api? Or that's largely a library duty to maintain? |
…modernize new code
…more complete commands for setting up manual testing.
path_finder
find_nvidia_headers.py
(Minimal Viable Product)find_nvidia_headers.py
for nvshmem
(Minimal Viable Product)
/ok to test |
Will it tolerate |
The code added in this PR ignores those completely. I've only tested these situations (copy-pasted from the current
Offline @leofang wrote that getting headers in general is now the top priority (I just created #832 to track the work). That will bring in Coming back to |
From offline with nvshmem team: if installed via apt package they go to |
Oh, @isVoid Is there another way people usually install
|
This aligns with my local testing as well. Sorry about the confusion! To support the python use case, we are only requesting the library to be discoverable when it's installed via |
Description
Currently no public API.
To support internal developments.