@@ -357,19 +357,19 @@ while retaining the option of building with Ninja on the command line.
357
357
358
358
Assuming that you have already [built the toolchain via Ninja](#the-actual-build),
359
359
several more steps are necessary to set up this environment:
360
- * Generate Xcode projects with `utils/build-script --release --swift-darwin-supported-archs "$(uname -m)" --xcode`.
360
+ * Generate Xcode projects with `utils/build-script --release --swift-darwin-supported-archs "$(uname -m)" --xcode --clean `.
361
361
This will first build a few LLVM files that are needed to configure the
362
362
projects.
363
363
* Create a new Xcode workspace.
364
364
* Add the generated Xcode projects or Swift packages that are relevant to your
365
365
tasks to your workspace. All the Xcode projects can be found among the
366
- build artifacts under `build/Xcode-DebugAssert `. For example:
367
- * If you are aiming for the compiler, add `build/Xcode-DebugAssert /swift-macosx-*/Swift.xcodeproj`.
366
+ build artifacts under `build/Xcode-ReleaseAssert `. For example:
367
+ * If you are aiming for the compiler, add `build/Xcode-ReleaseAssert /swift-macosx-*/Swift.xcodeproj`.
368
368
This project also includes the standard library and runtime sources. If you
369
369
need the parts of the compiler that are implemented in Swift itself, add the
370
370
`swift/SwiftCompilerSources/Package.swift` package as well.
371
371
* If you are aiming for just the standard library or runtime, add
372
- `build/Xcode-DebugAssert /swift-macosx-*/stdlib/Swift-stdlib.xcodeproj`.
372
+ `build/Xcode-ReleaseAssert /swift-macosx-*/stdlib/Swift-stdlib.xcodeproj`.
373
373
<!-- FIXME: Without this "hard" line break, the note doesn’t get properly spaced from the bullet -->
374
374
<br />
375
375
0 commit comments