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
1. Download ICU from [ICU Project](http://site.icu-project.org) for Windows x64 and extract the folder to a new folder called `thirdparty`. In other words, there should be a folder `S:\thirdparty\icu4c-64_2-Win64-MSVC2017` with the ICU.
56
-
1. Add the `bin64` folder to your `Path` environment variable.
54
+
## 3. Acquire ICU, SQLite3, curl, libxml2
55
+
1. Go to https://dev.azure.com/compnerd/windows-swift and scroll down to "Dependencies" where you'll see bots (hopefully green) for icu, SQLite, curl, and libxml2. Download each of the zip files and copy their contents into S:/Library. The directory structure should resemble:
- From within a **developer** command prompt (not PowerShell nor cmd, but the [Visual Studio Developer Command Prompt](https://msdn.microsoft.com/en-us/library/f35ctcxw.aspx)), execute the following command if you have an x64 PC.
66
+
## 4. Get ready
67
+
- From within a **NATIVE developer** command prompt (not PowerShell nor cmd, but the [Visual Studio Developer Command Prompt](https://msdn.microsoft.com/en-us/library/f35ctcxw.aspx)), execute the following command if you have an x64 PC (The Native Developer command prompt is situated at "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Visual Studio 2019\Visual Studio Tools\VC\x64 Native Tools Command Prompt for VS 2019.lnk").
72
68
73
-
```cmd
74
-
VsDevCmd -arch=amd64
75
-
```
69
+
Run this as administrator the first time, for setting up the symlinks below.
76
70
77
71
If instead you're compiling for a 32-bit Windows target, adapt the `arch` argument to `x86` and run
Warning: Creating the above links usually requires administrator privileges. The quick and easy way to do this is to open a second developer prompt by right clicking whatever shortcut you used to open the first one, choosing Run As Administrator, and pasting the above commands into the resulting window. You can then close the privileged prompt; this is the only step which requires elevation.
100
94
101
-
## 6. Build LLVM/Clang
95
+
## 5. Build LLVM/Clang
102
96
- This must be done from within a developer command prompt. Make sure that the build
103
97
type for LLVM/Clang is compatible with the build type for Swift. That is,
104
98
either build everything `Debug` or some variant of `Release` (e.g. `Release`,
@@ -124,7 +118,7 @@ ninja
124
118
```cmd
125
119
path S:\b\llvm\bin;%PATH%
126
120
```
127
-
## 7. Build CMark
121
+
## 6. Build CMark
128
122
- This must be done from within a developer command prompt.
129
123
130
124
```cmd
@@ -138,7 +132,7 @@ cmake -G Ninja^
138
132
ninja
139
133
```
140
134
141
-
## 8. Build Swift
135
+
## 7. Build Swift
142
136
- This must be done from within a developer command prompt
143
137
- Note that Visual Studio vends a 32-bit python 2.7 installation in `C:\Python27` and a 64-bit python in `C:\Python27amd64`. You may use either one based on your installation.
0 commit comments