Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
FSL
conda
docs
Commits
3d36fa85
Commit
3d36fa85
authored
Jul 30, 2021
by
Paul McCarthy
🚵
Browse files
DOC: small tweaks
parent
ae373664
Changes
2
Hide whitespace changes
Inline
Side-by-side
creating_fsl_conda_recipes.md
View file @
3d36fa85
...
...
@@ -259,7 +259,7 @@ when a new version of a project is released.
used to build a conda package to be overridden via the
`FSLCONDA_REPOSITORY`
and
`FSLCONDA_REVISION`
environment variables. To facilitate this, the project
source repository and git revision must be specified in the
`meta.yaml`
like
so (remembering that we have defined
`repository`
and
`version`
as
`jinja2
so (remembering that we have defined
`repository`
and
`version`
as
`jinja2
`
variables, above):
...
...
@@ -360,14 +360,10 @@ CUDA version that the package was built against.
To enable this, the
`meta.yaml`
file for a CUDA project needs to contain a
couple of additional elements. First, when a CUDA package is built, an
environment variable called `
CUDA_VER
` will be set in the environment,
containing the `
major.minor
` CUDA version the package is being built against -
this variable is set by the common FSL `
Makefile
` rules in the
[`
fsl/base
`](https://git.fmrib.ox.ac.uk/fsl/base) project.
The `
meta.yaml
` file can read this environment variable in as a `
jinja2
`
variable like so:
couple of additional elements. First, when a CUDA package is built, a variable
called
`CUDA_VER`
, containing the
`major.minor`
CUDA version the package is
being built against,
**must**
be set in the environment. The
`meta.yaml`
file
can read this environment variable in as a
`jinja2`
variable like so:
```
...
...
@@ -375,9 +371,9 @@ variable like so:
```
Built CUDA packages must be named
with
the version of CUDA they were
built
against
. This is accomplished by adding the CUDA version to the package
name
,
like so:
Built CUDA packages must be named
according to
the version of CUDA they were
built
against
, with a suffix of the form
`-cuda-X.Y`
. This is accomplished by
adding the CUDA version to the package
name like so:
```
...
...
development_workflow.md
View file @
3d36fa85
...
...
@@ -195,7 +195,7 @@ where:
projects.
For ex
m
aple, if the latest stable release for the
`fsl/base`
project is
For exa
m
ple, if the latest stable release for the
`fsl/base`
project is
`2106.1`
, and a new commit, with hash
`ac28d14`
, is subsequently pushed to the
`fsl/base`
master branch on 8 June 2021, the resulting development package
will be assigned the version string
`2106.1.post0.dev20210608+ac28d14`
.
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment