@@ -11,8 +11,8 @@ options can optionally be prefixed with `skbuild.`, for example
1111
1212## Verbosity
1313
14- You can increase the verbosity of the build with two settings - ` cmake .verbose`
15- is a shortcut for verbose build output, and logging.level controls
14+ You can increase the verbosity of the build with two settings - ` build .verbose`
15+ is a shortcut for verbose build output, and ` logging.level ` controls
1616scikit-build-core's internal logging. An example (with all configuration styles)
1717of setting both is:
1818
@@ -82,6 +82,12 @@ workaround for legacy tooling.
8282
8383:::
8484
85+ :::{versionchanged} 0.10
86+
87+ ` cmake.verbose ` was renamed to ` build.verbose ` .
88+
89+ :::
90+
8591## Minimum version & defaults
8692
8793Scikit-build-core, like CMake, has a special minimum required version setting.
@@ -114,6 +120,13 @@ requires = ["scikit-build-core>=0.10"]
114120minimum-version = " build-system.requires"
115121```
116122
123+ :::{versionchanged} 0.10
124+
125+ The ` "build-system.requires" ` option was added.
126+
127+ :::
128+
129+
117130:::{warning}
118131
119132The following behaviors are affected by ` minimum-version ` :
@@ -124,7 +137,8 @@ The following behaviors are affected by `minimum-version`:
124137- ` minimum-version ` 0.8+ (or unset) ` cmake.minimum-version ` and
125138 ` ninja.minimum-version ` are replaced with ` cmake.version ` and ` ninja.version ` .
126139- ` minimum-version ` 0.10+ (or unset) ` cmake.targets ` and
127- ` cmake.verbose ` are replaced with ` build.targets ` and ` build.verbose ` .
140+ ` cmake.verbose ` are replaced with ` build.targets ` and ` build.verbose ` . The
141+ CMake minimum version will be detected if not given.
128142
129143:::
130144
@@ -265,6 +279,12 @@ But you can also do more complex moves:
265279"mypackage/subpackage" = " python/src/subpackage"
266280```
267281
282+ :::{versionadded} 0.10
283+
284+ Support for the table form.
285+
286+ :::
287+
268288You can disable Python file inclusion entirely, and rely only on CMake's
269289install mechanism:
270290
@@ -310,8 +330,8 @@ wheel.exclude = ["**.pyx"]
310330
311331:::{versionchanged} 0.9
312332
313- Before scikit-build-core 0.9, these were matched on the source path, rather than
314- the wheel path, and didn't apply to CMake output.
333+ Previously these were matched on the source path, rather than the wheel path,
334+ and didn't apply to CMake output.
315335
316336:::
317337
@@ -475,10 +495,16 @@ CMAKE_ARGS: -DSOME_DEFINE=ON -DOTHER=OFF
475495You can also specify only specific targets to build (leaving this off builds the
476496default targets):
477497
478- ` ` ` {conftabs} cmake .targets ["python"]
498+ ` ` ` {conftabs} build .targets ["python"]
479499
480500```
481501
502+ :::{versionchanged} 0.10
503+
504+ ` cmake.targets ` was renamed to ` build.targets ` .
505+
506+ :::
507+
482508You can pass raw arguments directly to the build tool, as well:
483509
484510``` {conftabs} build.tool-args ["-j12", "-l13"]
@@ -600,13 +626,10 @@ remove = "dev0"
600626
601627This will remove the "dev" tag when it is equal to 0.
602628
603- ``` {versionadded} 0.5
604-
605- ```
606-
607- ``` {versionchanged} 0.10
629+ :::{versionchanged} 0.10
608630
609631Support for ` result ` and ` remove ` added.
632+
610633```
611634
612635:::
@@ -724,6 +747,10 @@ styles is possible with `reset`. These all can be chained, as well, so
724747Remember that you need to set the environment variable ` FORCE_COLOR ` to see
725748colors with pip.
726749
750+ ``` {versionadded} 0.10
751+
752+ ```
753+
727754## Other options
728755
729756You can select a custom build dir; by default scikit-build-core will use a
@@ -764,6 +791,10 @@ You can also fail the build with `fail = true`. This is useful with overrides if
764791you want to make a specific configuration fail. If this is set, extra
765792dependencies like ` "cmake" ` will not be requested.
766793
794+ ``` {versionadded} 0.10
795+
796+ ```
797+
767798## Overrides
768799
769800The overrides system allows you to customize for a wide variety of situations.
0 commit comments