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
Compiler Errors When Building From Source #194
Comments
You need the latest version of Xcode. |
I think you also need macOS 10.15 to be able to compile Swift 5.2. |
@sindresorhus, thanks for the quick response. So I installed Xcode 11.3.1 because according to this compatibility table, the latest version of Xcode MacOS Mojave 10.14.6 can run is 11.3.1: You are right about Swift 5.2. According to this post, "Swift 5.2 ships as part of Xcode 11.4" and from the wiki table linked above, the minimum macOS version for Xcode 11.4 is macOS 10.15.2. I can see in my "Build Settings" that I only have Swift 5 but not 5.2: Also, the I guess those 3 errors are the only Swift 5.2 features |
Correct |
Hello, I am trying to build from source but I keep running into two types of errors:
I am new to Swift. I have a solution but it requires modifying some Swift source code. I'm wondering why it doesn't compile right off the bat.
Machine information:
MacOS Mojave 10.14.6
Xcode 11.3.1
I installed
rustup
withbrew install rustup-init
and thenrustup-init
. I added~/.cargo/bin
toPATH
.I did
brew install gcc@9 SwiftLint
.I am on git tag
v2.7.1
.Signing Certificate Configuration:
I changed the signing certificate for Gifski project:
I changed the signing certificate for ShareExtension project:
Here is the diff from the certificate changes:
Build Errors:
Then I try to build a release version by going to the top menu "Product > Archive".
I get 3 errors total, but they are only of 2 different types:
My Solution:
I added extensions to
Sequence
that take in key paths because it looked like they were missing.Am I missing something? Is there a way to get it to build without adding those extensions?
The text was updated successfully, but these errors were encountered: