Skip to content

[docs] FAQ: Fix hardcoded arch in suggested build-script option. #63439

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

Merged
merged 1 commit into from
Feb 6, 2023
Merged

[docs] FAQ: Fix hardcoded arch in suggested build-script option. #63439

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/HowToGuides/FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,9 @@ The general idea is to build as little as you can.
aren't doing so already.
- Use `build-script`'s various `--skip-*` flags to skip configuring for
platforms that you do not care about.
- If you're on macOS, use `--swift-darwin-supported-archs="x86_64"`.
- Use a release build without assertions (`--release --no-assertions`).
While debuginfo and assertions are valuable to enable when working on the
- If you're on macOS, use `--swift-darwin-supported-archs "$(uname -m)"`.
- Build the release variant without assertions (`--release --no-assertions`).
While debug info and assertions are valuable to enable when working on the
toolchain itself, they are not so useful if you are working only on changes
to the build system.

Expand Down