Skip to content

Commit 31a367b

Browse files
Make the "unspecified" architecture option more general
1 parent 2f7e122 commit 31a367b

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/build/cmake-presets-vs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -264,7 +264,7 @@ The `architecture.strategy` and `toolset.strategy` values tell CMake how to hand
264264

265265
We recommend you use `set` with IDE generators like the Visual Studio Generator. Use `external` with command-line generators like Ninja. These values allow vendors like Visual Studio to supply the required environment before CMake is invoked. For more information about the architecture and toolset fields, see the [list of Configure Presets](https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html#configure-preset).
266266

267-
If Ninja is the generator and you don't want to source an environment, you can set `architecture.strategy` to `external` and `architecture.value` to `unspecified`. You might find it useful not to source an environment for any one of these reasons:
267+
If you don't want to source an environment, you can set `architecture.strategy` to `external` and `architecture.value` to `unspecified`. You might find it useful not to source an environment for any one of these reasons:
268268

269269
- You use a toolset other than MSVC.
270270
- You use a custom toolchain, such as in embedded scenarios.

0 commit comments

Comments
 (0)