Fix compiler nefc #54
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
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.
Issues
nefcfrom Swift 5.01 #49Description
we were using to link the user dependencies (Playground/Sources) + Apple Frameworks (.../Platform/Developer/Library/Frameworks) the option
-static-executable. It was working but it was a bug in the swift compiler, and now it has been solved. Darwin architectures (iOS, macos) does not allow statically linked binaries (it only allows static libs). You can read more information about it here.How does it implement?
we are compiling the user dependencies (Playground/Sources/*) together with the
page.swiftand using the options-Fto determinate where Apple frameworks are-Xlinkersearch recursively in the Apple Frameworks for selected SDK.On another hand, we have changed the SDK for iOS systems: from
iphonesimulator(x86_64) toiphoneos(arm*)