File tree Expand file tree Collapse file tree 1 file changed +4
-3
lines changed Expand file tree Collapse file tree 1 file changed +4
-3
lines changed Original file line number Diff line number Diff line change @@ -18,6 +18,7 @@ Currently three LAPACKE implementations are supported and tested:
18
18
- needs ` cmake ` and ` gfortran `
19
19
- [ Intel MKL] ( https://github.com/termoshtt/rust-intel-mkl ) (non-free license, see the linked page)
20
20
- needs ` curl `
21
+
21
22
There are two ways to link LAPACKE backend:
22
23
23
24
### backend features (recommended)
@@ -26,7 +27,7 @@ There are three features corresponding to the backend implementations (`openblas
26
27
``` toml
27
28
[dependencies ]
28
29
ndarray = " 0.12"
29
- ndarray-linalg = { version = " 0.9 " , features = [" openblas" ] }
30
+ ndarray-linalg = { version = " 0.10 " , features = [" openblas" ] }
30
31
```
31
32
32
33
### link backend crate manually
@@ -36,7 +37,7 @@ You should link a LAPACKE implementation to a final crate (like binary executabl
36
37
``` toml
37
38
[dependencies ]
38
39
ndarray = " 0.12"
39
- ndarray-linalg = " 0.9 "
40
+ ndarray-linalg = " 0.10 "
40
41
openblas-src = " 0.5" # or another backend of your choice
41
42
42
43
```
@@ -55,7 +56,7 @@ If you creating a library depending on this crate, we encourage you not to link
55
56
``` toml
56
57
[dependencies ]
57
58
ndarray = " 0.12"
58
- ndarray-linalg = { version = " 0.9 " , default-features = false }
59
+ ndarray-linalg = { version = " 0.10 " , default-features = false }
59
60
```
60
61
61
62
However, if you hope simplicity instead of the flexibility, you can link your favorite backend in the way described above.
You can’t perform that action at this time.
0 commit comments