Skip to content

Commit 9f69e65

Browse files
committed
docs: add pointer to itk
This is an example of a realistic, more complex scikit-build-core SWIG project that also sparked the origin of scikit-build. Point to the main `itk` package pyproject.toml configuration and many adition ITK Remote Module extension packages configured here many additional examples referenced here: InsightSoftwareConsortium/ITK#4748
1 parent 411d2c4 commit 9f69e65

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

docs/projects.md

+7
Original file line numberDiff line numberDiff line change
@@ -53,3 +53,10 @@ In addition, most of the [RAPIDSAI](https://github.com/rapidsai) projects use sc
5353
* CuSpatial ([source](https://github.com/rapidsai/cuspatial/blob/HEAD/python/cuspatial/pyproject.toml))
5454
* RMM ([source](https://github.com/rapidsai/rmm/blob/HEAD/python/rmm/pyproject.toml))
5555
* Raft ([source](https://github.com/rapidsai/raft/blob/HEAD/python/pylibraft/pyproject.toml))
56+
57+
The [Insight Toolkit (ITK)](https://docs.itk.org), the initial target project
58+
for scikit-build classic, has [transitioned to
59+
sckit-build-core](https://github.com/InsightSoftwareConsortium/ITKPythonPackage/blob/master/scripts/pyproject.toml.in).
60+
ITK currently provides one example of a production SWIG-based deployment. In
61+
addition, dozens of [ITK-based extension packages are configured with
62+
scikit-build-core](https://github.com/InsightSoftwareConsortium/ITK/issues/4748).

0 commit comments

Comments
 (0)