Skip to content

Conversation

@rjmansfield
Copy link
Contributor

Previously when SWIFT_EXEC or SWIFT_EXEC_MANIFEST were set to non-existent or non-executable paths, swiftpm would silently ignore them and fall back to the default Swift compiler. This caused confusion during development when typos or incorrect paths were used.

@rjmansfield
Copy link
Contributor Author

@swift-ci test

Copy link
Contributor

@jakepetroules jakepetroules left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We want to avoid writing to standard output streams in library code. Can you plumb an ObservabilityScope down to this method instead?

@rjmansfield rjmansfield force-pushed the warn-invalid-swift-exec branch from 5586e17 to 843ba4a Compare November 11, 2025 05:04
Previously when SWIFT_EXEC or SWIFT_EXEC_MANIFEST were set to non-existent
or non-executable paths, swiftpm would silently ignore them and fall back to
the default Swift compiler. This caused confusion during development when
typos or incorrect paths were used.
@rjmansfield rjmansfield force-pushed the warn-invalid-swift-exec branch from 843ba4a to 0884fb1 Compare November 11, 2025 14:53
@rjmansfield
Copy link
Contributor Author

@swift-ci test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants