-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
OS X Universal Binary Support #2024
Comments
Looks like #2084 blocks this. |
Is this still non-universal? The MacPorts port for Rust includes a +universal variant, and I'm just wondering if it does anything, or if I should remove it. |
(and by "or if I should remove it", I actually mean "or if I should have @g5pw remove it".) |
It's been a year, and I don't own a mac. Is 32-bit support still relevant? What range of OS X does Rust support? |
10.6+ |
Can’t you target 32-bit by specifying |
By the way, it seems that the highest version of Mac OS X that a PPC Mac can run is 10.5.8, and since we don't support anything < 10.6 anyway, we don't need to worry about PPC. IA32, however, can run 10.6.8. Not sure how important it is. |
Nominating for milestone 3, feature-complete |
just a bug, removing milestone/nomination. |
Still an issue, but it feels like we're not going to implement this by the time Apple drops support for Snow Leopard anyway |
Still an issue. I feel like it's pretty unimportant ATM. |
With the upcoming transition to Apple Silicon it might become important to support Univeral Binaries. |
Co-authored-by: Celina G. Val <[email protected]>
* linkcheck: fix reported broken links (part 2) * Apply suggestions from code review Co-authored-by: León Orell Valerian Liehr <[email protected]> * Fix mir::Constant link target * Fix borked links * Fix one more link name * Exclude 2 links from checking * Fix exclude patterns in book.toml * Fix comment * Fix rmake-tests URL * Apply suggestions from code review Co-authored-by: León Orell Valerian Liehr <[email protected]> --------- Co-authored-by: León Orell Valerian Liehr <[email protected]>
* linkcheck: fix reported broken links (part 2) * Apply suggestions from code review Co-authored-by: León Orell Valerian Liehr <[email protected]> * Fix mir::Constant link target * Fix borked links * Fix one more link name * Exclude 2 links from checking * Fix exclude patterns in book.toml * Fix comment * Fix rmake-tests URL * Apply suggestions from code review Co-authored-by: León Orell Valerian Liehr <[email protected]> --------- Co-authored-by: León Orell Valerian Liehr <[email protected]>
On OS X a number of libraries are built universally. At the very least, it would be nice to tell
rustc
if your planning on targeting 32 or 64 bit in case your building against a library that is currently only available as one or the other. Currently, I think the only way of doing this is to specify a host triple at compile time and build the entire system as one or the other. It would be nice to be able to build universally on OS X and support targeting a specific architecture. The gcc and clang both support-m32
or-m64
as a simple solution to specifying the architecture, as well as-arch
flags.With clang and gcc
-arch
can be used to specify which architectures you want to build for, for exampleclang foo.c -o foo.o -arch i386 -arch x86_64 -arch ppc
will tell the compiler to build a binary that supports 3 different architectures.The text was updated successfully, but these errors were encountered: