Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
B
base
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
FSL
base
Commits
caec24f2
Commit
caec24f2
authored
3 years ago
by
Paul McCarthy
Browse files
Options
Downloads
Patches
Plain Diff
DOC: Some notes on CUDA builds
parent
b267a76b
No related branches found
No related tags found
1 merge request
!14
Rf/cuda linking
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+16
-0
16 additions, 0 deletions
README.md
with
16 additions
and
0 deletions
README.md
+
16
−
0
View file @
caec24f2
...
@@ -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
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment