File tree Expand file tree Collapse file tree 1 file changed +6
-2
lines changed Expand file tree Collapse file tree 1 file changed +6
-2
lines changed Original file line number Diff line number Diff line change @@ -241,7 +241,7 @@ various products. These incremental builds are a big timesaver when developing
241
241
and debugging.
242
242
243
243
cd ${SWIFT_BUILD_DIR}
244
- ninja swift
244
+ ninja compiler
245
245
246
246
This will build the Swift compiler, but will not rebuild the standard library or
247
247
any other target. Building the ` swift-stdlib ` target as an additional layer of
@@ -250,6 +250,10 @@ library, run:
250
250
251
251
ninja swift-stdlib
252
252
253
+ To build just the compiler frontend, run:
254
+
255
+ ninja swift-frontend
256
+
253
257
It is always a good idea to do a full build after using ` update-checkout ` .
254
258
255
259
#### Using Xcode
@@ -258,7 +262,7 @@ To open the Swift project in Xcode, open `${SWIFT_BUILD_DIR}/Swift.xcodeproj`.
258
262
It will auto-create a * lot* of schemes for all of the available targets. A
259
263
common debug flow would involve:
260
264
261
- - Select the 'swift' scheme.
265
+ - Select the 'swift-frontend ' scheme.
262
266
- Pull up the scheme editor (⌘⇧<).
263
267
- Select the 'Arguments' tab and click the '+'.
264
268
- Add the command line options.
You can’t perform that action at this time.
0 commit comments