Skip to content
Snippets Groups Projects
Commit caec24f2 authored by Paul McCarthy's avatar Paul McCarthy :mountain_bicyclist:
Browse files

DOC: Some notes on CUDA builds

parent b267a76b
No related branches found
No related tags found
1 merge request!14Rf/cuda linking
...@@ -16,3 +16,19 @@ Prior to FSL 6.1.X, the contents of this project were provided by the ...@@ -16,3 +16,19 @@ Prior to FSL 6.1.X, the contents of this project were provided by the
The `.ci` directory contains a collection of tests which validate the The `.ci` directory contains a collection of tests which validate the
behaviour of various aspects of the `base` project. All tests are written behaviour of various aspects of the `base` project. All tests are written
in Python, and are executed with `pytest`. in Python, and are executed with `pytest`.
## CUDA build options
The following options may be used to control compilation of a CUDA project:
- `CUDA_HOME`: Specify the path to the CUDA installation directory
- `CUDA_STATIC`: Statically link against the CUDA runtime and certain;
CUDA Toolkit libraris (default is to use dynamic linking).
- `GENCODEFLAGS`: `-gencode` options specifying the device architectures to
compile device code for (default is to use the
`config/supportedGencodes.sh` script).
For example, to compile a CUDA project with a specific CUDA installation, and
using static linking:
make CUDA_STATIC=1 CUDA_HOME=/usr/local/cuda-10.1
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment