https://github.com/eneko/swiftpmargumentissue
https://github.com/eneko/swiftpmargumentissue
Last synced: 3 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/eneko/swiftpmargumentissue
- Owner: eneko
- Created: 2021-12-06T16:00:16.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2021-12-06T16:10:02.000Z (over 3 years ago)
- Last Synced: 2025-02-09T07:25:06.955Z (5 months ago)
- Language: Swift
- Size: 1.95 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# SwiftPMArgumentIssue
This repo contains a simple Swift executable created
with Swift Package Manager. This executable has the
only purpose to illustrate an issue with Swift Package
Manager taking over arguments intended for the executable
when run with `swift run` from the command line.
Executable code:
```swift
print("Hello, world!")
print("Arguments: \(CommandLine.arguments)")
```
Example run:
```
$ swift run
[0/0] Build complete!
Hello, world!
Arguments: [".build/x86_64-apple-macosx/debug/SwiftPMArgumentIssue"]
```
## Argument Collision
The issue is when passing arguments that clash with SwiftPM own
arguments.
### Passing a non-colliding argument
```
$ swift run SwiftPMArgumentIssue --foo bar
[0/0] Build complete!
Hello, world!
Arguments: [".build/x86_64-apple-macosx/debug/SwiftPMArgumentIssue", "--foo", "bar"]
```
Passing any argument used by SwiftPM causes unexpected results.
### Passing `--verbose`
```
$ swift run SwiftPMArgumentIssue --foo bar --verbose
/usr/bin/xcrun --sdk macosx --show-sdk-platform-path
/Applications/Xcode13.2b2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc -print-target-info
/usr/bin/xcrun --sdk macosx --find xctest
/Applications/Xcode13.2b2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc -print-target-info
/Applications/Xcode13.2b2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-frontend -frontend -print-target-info -sdk /Applications/Xcode13.2b2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.1.sdk
/Applications/Xcode13.2b2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-frontend -frontend -print-target-info
/Applications/Xcode13.2b2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-frontend -frontend -emit-supported-features /var/folders/bm/5ty7rqlx5579jr38d16pzy0m0000gr/T/TemporaryDirectory.UoOW68/dummyInput-1.swift
/usr/bin/xcrun --sdk macosx --show-sdk-platform-path
/usr/bin/xcrun vtool -show-build /Applications/Xcode13.2b2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks/XCTest.framework/XCTest
/usr/bin/xcrun --sdk macosx --show-sdk-platform-path
/usr/bin/xcrun vtool -show-build /Applications/Xcode13.2b2.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks/XCTest.framework/XCTest
/usr/bin/xcrun --sdk iphoneos --show-sdk-platform-path
/usr/bin/xcrun vtool -show-build /Applications/Xcode13.2b2.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/Frameworks/XCTest.framework/XCTest
/usr/bin/xcrun --sdk appletvos --show-sdk-platform-path
/usr/bin/xcrun vtool -show-build /Applications/Xcode13.2b2.app/Contents/Developer/Platforms/AppleTVOS.platform/Developer/Library/Frameworks/XCTest.framework/XCTest
/usr/bin/xcrun --sdk watchos --show-sdk-platform-path
/usr/bin/xcrun vtool -show-build /Applications/Xcode13.2b2.app/Contents/Developer/Platforms/WatchOS.platform/Developer/Library/Frameworks/XCTest.framework/XCTest
[0/0] Build complete!
Hello, world!
Arguments: [".build/x86_64-apple-macosx/debug/SwiftPMArgumentIssue", "--foo", "bar"]
```
Note how `--verbose` was used by `swift run` instead of our
executable.
### Passing `-c`:
```
$ swift run SwiftPMArgumentIssue --foo bar -c 200
error: The value '200' is invalid for '-c '
Help: -c Build with configuration
Usage: swift run [] [] [ ...]
See 'run -help' for more information.
```
In this case, `-c` is mistakenly being used by SwiftPM again,
which expects configuration to be either "debug" or "release". It
is impossible to pass `-c` to our executable being run.