-
Notifications
You must be signed in to change notification settings - Fork 125
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
Trying to cross compile zeromq-src for aarch64-apple-ios #173
Comments
I also hit this trying to compile a different crate for iOS.
That doesn't look to me like it would have caused this, but #110 added the code you linked to set |
You're correct on this count, however. I was able to get past the |
Aha, it looks like #158 caused this issue! I assume that setting |
That PR I created adds an iOS cross-compile test, which reproduces the failure here. I'm going to try simply removing that block of code that sets |
…Fixes rust-lang#173 In rust-lang#158, better support for using CMake's cross-compilation facilities was added. This made the workaround added in rust-lang#110 for iOS not only unnecessary, but actively harmful, in that it runs afoul of SDK validation checks in the CMake iOS codepath.
@blu3beri thanks for filing this issue with so much detail! It was helpful in figuring out a fix. |
hi
I am currently trying to compile zeromq-src (0.1.10+4.3.2) and it seems to error that cmake can not find the iOS sdk.
aarch64-apple-ios
(or any apple-ios target)This part of the stack trace caught my eye:
After doing some digging in cmake-rs it seems to be related to this line here https://github.com/rust-lang/cmake-rs/blob/07cbf8fd36168b8a5dc9e107f6e659130dbcdd30/src/lib.rs.
This sets the
CMAKE_OSX_SYSROOT
to/
and afterwards this code executes within cmake:After this code, this executes:
I do not know almost anything about cmake, but this does seem very weird and I am unsure how I can resolve this.
Reproduce (on MacOS)
Happy to provide more information about my system where required.
Stacktrace
EDIT
It seems that the release of 0.1.49 caused this issue, likely from this PR: #160
The text was updated successfully, but these errors were encountered: