Developer: Fix certain Swiftgen installations #794
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Can confirm that this PR fixes the build failing on ASi due to Swiftgen. |
|
Thank you! I still have my old Homebrew installation before they migrated installation destinations so it's always worked for me. |
LePips
approved these changes
Jun 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When running scripts from an Apple Silicon Mac, the
$PATHis different from your user's$PATH(see this discussion). Sincecontributing.mdsuggests you install Swiftgen using Homebrew, we should definitely be supporting this use case as well as we possibly can.Furthermore, a cryptic
Command PhaseScriptExecution failed with a nonzero exit codeappears when Swiftgen is not found, so I added a new error instructing developers to go tocontributing.mdfor installation instructions.