docs.rs failed to build cuda-bindings-0.3.1
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
cuda-bindings
Generated raw Rust FFI bindings to the CUDA toolkit libraries used by this workspace.
This crate is intentionally low level. Most code should depend on cuda-core instead of calling these bindings directly.
Notes
- The bindings are generated at build time from a CUDA 13.0+ toolkit.
- The toolkit root is the first set variable among
CUDA_TOOLKIT_PATHandCUDA_HOME; when neither is set, the build searches the standard install locations (on Linux/usr/local/cuda-13.3,/usr/local/cuda-13.2,/usr/local/cuda-13,/usr/local/cuda; on WindowsC:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v13.3andv13.2). - Within the toolkit, both the standard
include/layout and the redistributabletargets/<dir>/include/layouts (Jetson/Tegra, sbsa, cross-builds, extracted redistributables) are probed forcuda.h.CUDA_TOOLKIT_TARGET_DIRnames onetargets/directory by hand, like nvcc's-target-dirflag; when set, that tree is the only candidate probed. - Set
CUTILE_SETUP_DIAGNOSTICS=1to print CUDA toolkit discovery decisions.