Skip to content

Commit e648af7

Browse files
authored
Update README.md
Update README.md to be more concise about the environment variables.
1 parent 778e896 commit e648af7

File tree

1 file changed

+5
-40
lines changed

1 file changed

+5
-40
lines changed

README.md

Lines changed: 5 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -28,48 +28,13 @@ ninja -C build SwiftWin32 UICatalog
2828
%CD%\build\bin\UICatalog.exe
2929
```
3030

31-
Following environment variables should be set/adjusted before run the above commands (the shown paths assume that you use compiler from the official swift installers from [swift.org](https://www.swift.org/download/)).
32-
33-
- Visual Studio compiler toolchain
34-
35-
The CMake commands use the `mt` tool which requires a Visual Studio compiler environment (Build Tools should be fine too).
36-
e.g. if you have Visual Studio 2019 installed you can create a command prompt by click on `x64 Native Tools Command Prompt for VS2019` from the Visual Studio 2019 installation in the Windows Start Menu.
37-
38-
Newer versions of Visual Studio or the corresponding Build Tools should be fine too.
39-
40-
Another way of activating a Visual Studio environment is the tool [vswhere](https://github.com/microsoft/vswhere).
41-
42-
- `SDKROOT`
43-
44-
This should be the path to the Windows Platform SDK from the Swift library. This should be already set by the official swift installer. If not set the env var.
45-
46-
\>= 5.10 `SDKROOT` needs to be `%LocalAppData%\Programs\Swift\Platforms\Windows.platform\Developer\SDKs\Windows.sdk`
47-
48-
< 5.10 `SDKROOT` needs to be `%SystemDrive%\Library\Developer\Platforms\Windows.platform\Developer\SDKs\Windows.sdk`
49-
50-
Examples for < 5.10:
51-
52-
Command Prompt: `set SDKROOT=%SystemDrive%\Library\Developer\Platforms\Windows.platform\Developer\SDKs\Windows.sdk`
53-
54-
PowerShell: `$env:SDKROOT="%SystemDrive%\Library\Developer\Platforms\Windows.platform\Developer\SDKs\Windows.sdk"`
55-
56-
- `Path`
57-
58-
The `Path` environment variables needs to be extended to allow the Swift compiler to be found.
59-
This is only required when this is not already the case.
60-
When you type `where swiftc` (`(Get-Command swiftc).Path` for PowerShell) and see no path to `swiftc` the following command is required.
61-
62-
\>= 5.10 the `Path` needs to extended with `%LocalAppData%\Programs\Swift\Runtimes\5.9.0\usr\bin;%LocalAppData%\Programs\Swift\Toolchains\5.9.0+Asserts\usr\bin`
63-
64-
< 5.10 the `Path` needs to be extended with `%SystemDrive%\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin`
65-
66-
Examples for < 5.10:
67-
68-
Command Prompt: `set Path=%SystemDrive%\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin;%Path%`
69-
70-
PowerShell: `$env:Path="%SystemDrive%\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin;$env:Path"`
31+
<details>
32+
<summary>Required Environment Variables</summary>
7133

34+
The CMake build will automatically perform the application manifest merging via the `mt` tool, which is part of the Visual Studio build tools. Ensure that you run the build under the `x64 Native Tools Command Prompt for VS2019` (or the appropriate shell for the version of Visual Studio).
7235

36+
The Swift installer will also add environment variables, ensure that you have restarted the terminal emulator after installing the toolchain to pick up the required environment variables.
37+
</details>
7338

7439
### Swift Package Manager
7540

0 commit comments

Comments
 (0)