You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upgrade to libtorch 2.7.1 and cuda 12.8, create new proj files for the new fragments and change linux cuda and windows cuda jobs to not run in parallel
Copy file name to clipboardExpand all lines: DEVGUIDE.md
+18-16Lines changed: 18 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,8 +110,8 @@ For this reason, we do the following
110
110
1. The head, referenceable packages that deliver a functioning runtime are any of:
111
111
112
112
libtorch-cpu
113
-
libtorch-cuda-12.1-linux-x64
114
-
libtorch-cuda-12.1-win-x64
113
+
libtorch-cuda-12.8-linux-x64
114
+
libtorch-cuda-12.8-win-x64
115
115
116
116
2. These packages are combo packages that reference multiple parts. The parts are **not** independently useful.
117
117
Some parts deliver a single vast file via `primary` and `fragment` packages. A build task is then used to "stitch" these files back together
@@ -120,7 +120,7 @@ For this reason, we do the following
120
120
install/detect/link of PyTorch CUDA on all downstream systems, whcih is extremely problematic
121
121
for many practical reasons).
122
122
123
-
For example, the CUDA package fragments are defined in [libtorch-cuda](src/Redist/libtorch-cuda-12.1/libtorch-cuda-12.1.proj). See more details later in this document.
123
+
For example, the CUDA package fragments are defined in [libtorch-cuda](src/Redist/libtorch-cuda-12.8/libtorch-cuda-12.8.proj). See more details later in this document.
124
124
125
125
3. The `libtorch-*` packages are built in Azure DevOps CI
126
126
[using this build pipeline](https://donsyme.visualstudio.com/TorchSharp/_build?definitionId=1&_a=summary) but only in main
@@ -166,12 +166,12 @@ version of PyTorch then quite a lot of careful work needs to be done.
166
166
167
167
To update the version, update this in [Dependencies.props](build/Dependencies.props):
168
168
169
-
<LibTorchVersion>2.2.0</LibTorchVersion>
169
+
<LibTorchVersion>2.7.1</LibTorchVersion>
170
170
171
171
The libtorch version number is also referenced in source code, in the file 'src/TorchSharp/Torch.cs':
172
172
173
173
```C#
174
-
conststringlibtorchPackageVersion="2.2.0.1";
174
+
conststringlibtorchPackageVersion="2.7.1.0";
175
175
```
176
176
177
177
3. RunthesetotestdownloadsandupdateSHAhashesfor the various LibTorch downloads
Each of these will take a **very very long time** depending on your broadband connection. This can't currently be done in CI.
202
+
Each of these can take a **very very long time** depending on your broadband connection. This can't currently be done in CI.
203
203
204
204
If file names in the distribution have changed, or files have been removed, you will get errors saying that files cannot be found. That's okay and will be taken care of in the next step.
205
205
206
206
4. At this point you must **very very carefully** update the `<File Include= ...` entries under src\Redist projects for
207
-
[libtorch-cpu](src/Redist/libtorch-cpu/libtorch-cpu.proj) and [libtorch-cuda](src/Redist/libtorch-cuda-12.1/libtorch-cuda-12.1.proj).
207
+
[libtorch-cpu](src/Redist/libtorch-cpu/libtorch-cpu.proj) and [libtorch-cuda](src/Redist/libtorch-cuda-12.8/libtorch-cuda-12.8.proj).
bytesthatisthelimit, **not**250*1024*1024. Inotherwords, itis250MB, not250MiB. NotethatWindowsExplorerwillshowfilesizesinKiB, notthousandsofbytes. Use'dir'fromaCMDwindowtogettheexactsizeinbytesfor each file. For example -- the file `libtorch_cpu.so` shows up as 511,872 KB in Windows Explorer, but 524,156,144 bytes in CMD. The 2.4% difference can be significant. Getting the partitioning right requires precision.
0 commit comments