Skip to content

Commit

Permalink
Escape JLL names in documentation.
Browse files Browse the repository at this point in the history 
[skip tests]
  • Loading branch information
@maleadt
maleadt authored Feb 7, 2023
1 parent 82c7df2 commit 0dce8ca
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/src/installation/overview.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -129,7 +129,7 @@ This generates the following `LocalPreferences.toml` file in your active environ
version = "11.8"
```

This preference is compatible with other CUDA JLLs, e.g., if you load CUDNN_jll it will
This preference is compatible with other CUDA JLLs, e.g., if you load `CUDNN_jll` it will
only select artifacts that are compatible with the configured CUDA runtime.

### Using a local CUDA
Expand Down Expand Up @@ -175,7 +175,7 @@ binaries aren't on a globally-discoverable path. For more information, run Julia
`JULIA_DEBUG` environment variable set to `CUDA_Runtime_Discovery`.

Note that setting the version to `"local"` disables use of *any* CUDA-related JLL, not just
of CUDA_Runtime_jll. This is out of necessity: JLLs are baked in the precompilation image at
of `CUDA_Runtime_jll`. This is out of necessity: JLLs are baked in the precompilation image at
compile time, while local toolkit discovery happens at run time; this inconsistency makes it
impossible to select a compatible artifact for the JLLs. If you care about other JLLs, use
CUDA from artifacts.
Expand Down

0 comments on commit 0dce8ca

Please sign in to comment.