Skip to content

Commit

Permalink
docs: Remove explicit CUDA version numbers shown as examples
Browse files Browse the repository at this point in the history
* Remove any explicit CUDA version number shown as an example to avoid
  recommending outdated versions. Instead, use <CUDA VERSION> for something
  like '11.2' and cuda<version> for something like 'cuda112', or point
  to the cuda-feedstock user guides.
  • Loading branch information
matthewfeickert committed Jan 8, 2025
1 parent 8f5d2d1 commit 35646a1
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 5 deletions.
2 changes: 1 addition & 1 deletion docs/maintainer/adding_pkgs.md
Original file line number Diff line number Diff line change
Expand Up @@ -893,7 +893,7 @@ $ cd ~/staged-recipes
$ python build-locally.py <VARIANT>
```

where `<VARIANT>` is one of the file names in the `.ci_support/` directory, e.g. `linux64`, `osx64`, and `linux64_cuda102`.
where `<VARIANT>` is one of the file names in the `.ci_support/` directory, e.g. `linux64`, `osx64`, and `linux64_cuda<version>`.

<a id="about"></a>

Expand Down
2 changes: 1 addition & 1 deletion docs/maintainer/infrastructure.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ The YAML files included in `.ci_support` are minimal and not rendered like the o
Instead, conda-build will take these and combine them with the pinnings from `conda-forge-pinning` at runtime.
Also note that `staged-recipes` only builds for x64. Support for additional architectures can only be done once a feedstock has been provided.

- Linux: `linux64.yaml` plus the CUDA (10.2, 11.0, 11.1 and 11.2) variants.
- Linux: `linux64.yaml` plus the CUDA variants.
- macOS: `osx64.yaml`.
- Windows `win64.yaml`.

Expand Down
7 changes: 4 additions & 3 deletions docs/user/tipsandtricks.md
Original file line number Diff line number Diff line change
Expand Up @@ -143,14 +143,15 @@ In conda-forge, some packages are available with GPU support. These packages not
In order to override the default behavior, a user can set the environment variable `CONDA_OVERRIDE_CUDA` like below to install TensorFlow with GPU support even on a machine with CPU only.

```shell-session
CONDA_OVERRIDE_CUDA="11.2" conda install "tensorflow==2.7.0=cuda112*" -c conda-forge
CONDA_OVERRIDE_CUDA="<CUDA version>" conda install "tensorflow==2.7.0=cuda<version>*" -c conda-forge
# OR
CONDA_OVERRIDE_CUDA="11.2" mamba install "tensorflow==2.7.0=cuda112*" -c conda-forge
CONDA_OVERRIDE_CUDA="<CUDA version>" mamba install "tensorflow==2.7.0=cuda<version>*" -c conda-forge
```

:::note

You should select the cudatoolkit version most appropriate for your GPU; currently, we have "10.2", "11.0", "11.1", and "11.2" builds available, where the "11.2" builds are compatible with all cudatoolkits>=11.2. At the time of writing (Mar 2022), there seems to be a bug in how the CUDA builds are resolved by `mamba`, defaulting to `cudatoolkit==10.2`; thus, it is prudent to be as explicit as possible like above or by adding `cudatoolkit>=11.2` or similar to the line above.
You should select the `cuda-toolkit` version most appropriate for your GPU.
See the [relevant CUDA user guides](https://github.com/conda-forge/cuda-feedstock/blob/main/recipe/README.md) for more information.

:::

Expand Down

0 comments on commit 35646a1

Please sign in to comment.