-
Notifications
You must be signed in to change notification settings - Fork 49
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
Update dependencies, Xcode version and minimum deployment target #530
Conversation
The versions supported by Rust was updated in rust-lang/rust#104385 to: - macOS: 10.12 Sierra - iOS: 10.0 - tvOS: 10.0 - watchOS: 5.0 Additionally, the armv7-apple-ios target was removed. Finally, since v1.0.84 of `cc` (has been yanked, but 1.0.85 will include it as well), there is much better support for specifying the deployment target for Apple targets, so I've removed the corresponding code from objc-sys.
bfd09a5
to
1f241be
Compare
pop {r7, lr} | ||
b _objc_retainAutoreleasedReturnValue |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the fast autoreleasing may have been broken by this change on armv7s-apple-ios
:(.
Unsure how to fix that?
| / declare_class!( | ||
| | struct CustomObject; | ||
| | | ||
| | unsafe impl ClassType for CustomObject { | ||
... | | ||
| | } | ||
| | ); | ||
| |_^ the trait `MessageReceiver` is not implemented for `CustomObject` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find that the compiler is often changing between these two, unfortunately we've gotten the worse end of the stick currently.
@@ -61,7 +61,7 @@ unstable-exception = ["cc"] | |||
unstable-docsrs = [] | |||
|
|||
[build-dependencies] | |||
cc = { version = "1", optional = true } | |||
cc = { version = "1.0.80", optional = true } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be 1.0.84
, but that was yanked, so we'll just suggest a high value for now.
2dbf3e2
to
041c030
Compare
Previously, we were calling `sel!` before the inner expression, which increases stack pressure because the compiler doesn't know it's allowed to defer loading the selector until just before it needs it.
I had to modify the struct/typedef code a bit, since clang now does those differently.
And make it more visible in the future
No description provided.