Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update README for new target names #32701

Merged
merged 2 commits into from Jul 4, 2020
Merged

Update README for new target names #32701

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1f9da38
Update README for new target names
Jumhyn Jul 3, 2020
7332619
Remove `ninja compiler` command
Jumhyn Jul 3, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 6 additions & 2 deletions README.md
View file
Open in desktop
Expand Up @@ -241,7 +241,7 @@ various products. These incremental builds are a big timesaver when developing
and debugging.

cd ${SWIFT_BUILD_DIR}
ninja swift
ninja compiler
varungandhi-apple marked this conversation as resolved.
Show resolved Hide resolved

This will build the Swift compiler, but will not rebuild the standard library or
any other target. Building the `swift-stdlib` target as an additional layer of
Expand All @@ -250,6 +250,10 @@ library, run:

ninja swift-stdlib

To build just the compiler frontend, run:

ninja swift-frontend

It is always a good idea to do a full build after using `update-checkout`.

#### Using Xcode
Expand All @@ -258,7 +262,7 @@ To open the Swift project in Xcode, open `${SWIFT_BUILD_DIR}/Swift.xcodeproj`.
It will auto-create a *lot* of schemes for all of the available targets. A
common debug flow would involve:

- Select the 'swift' scheme.
- Select the 'swift-frontend' scheme.
- Pull up the scheme editor (⌘⇧<).
- Select the 'Arguments' tab and click the '+'.
- Add the command line options.
Expand Down