-
-
Notifications
You must be signed in to change notification settings - Fork 59
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.
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
Running script in iOS project as build-script fails #113
Comments
I'm having the same problem after updating to Xcode 11.4 |
Any update? |
Try using |
Hi everyone, I have finally got some time together to fix this. I’m pretty sure the fix is a one liner. It's depressing to me that my open source is totally dependent on what time I have to give it 😞 I'm not sure really what I could do to have made any of you felt confident enough to submit a PR. |
So, in theory #113 fixes it, but I could use a test-case. |
2.0.1 has the fix. Please try! |
@mxcl I just ugpraded to 2.0.1 but I'm still having the same issue: /Users/Jeehut/Library/Developer/swift-sh.cache/6cfae87d4ff40300d031fc7f93264221: error: manifest parse error(s):
<unknown>:0: warning: using sysroot for 'iPhoneSimulator' but targeting 'MacOSX'
<unknown>:0: error: unable to load standard library for target 'x86_64-apple-macosx10.15'
error: 1 <(/Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift build -Xswiftc -suppress-warnings) The funny thing is, when I switch to my macOS target, build (same build script there, running |
I've just tried to run a Swift script using
swift-sh
in the Xcode build scripts step in an iOS project and it failed with the following output:This seems to be a known issue (SR-9216 – feel free to click the "Vote for this issue" button) but it's open for over a year now, so I suggest we add a workaround into swift-sh and don't wait for it to be fixed.
The simplest workaround seems to be using
#!/usr/bin/xcrun --sdk macosx swift
, so we might want to use that to execute Swift as well somehow. See also this Swift Forums thread.The text was updated successfully, but these errors were encountered: