-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
Why @rules_cuda//cuda:runtime
flag rather than respecting --dynamic_mode
#119
Comments
This is from Lines 91 to 103 in 152bbbc
|
@cloudhan are you OK with me removing the flag and just relying on |
I don't know the reason behind it actually, so let's keep it as is for now. Maybe @chsigg can explain it a bit? |
The flag is also introduced to inject a different CUDA runtime, e.g. one that dynamically loads the real CUDA runtime and forwards the calls. That can be independent though of (by default) dynamically switching between linking against static or dynamic runtime. I don't know how to dynamically switch between the two based on |
If you assign this to me I can work on making it respect |
Bazel already has a flag (
--dynamic_mode
) to allow controlling of static vs dynamic linking. I think it's feasible to apply this to the cuda runtime. Why not use this flag? It's surprising that there's a separate flag and that the bazel flag is not respected.If you're OK with switching to use the built-in
--dynamic_mode
I'd be happy to open a PR to implement the change.Thanks!
The text was updated successfully, but these errors were encountered: