Update toolchain to support Apple Sillicon - 2025 edition #136
Conversation
This allows detecting newer platforms like Apple Silicon. Also update the commands to use `cmake -E env`.
- Download from github rather than pyyaml. - Update to the latest version (0.2.5). - Use `cmake -E env` to invoke the wrapper command.
- Run autoreconf to fix flat namespace issues on macOS 11+. - Don't use the command wrapper to build, this breaks on arm64 linux.
This adds support for Apple Silicon.
This adds Apple Silicon support.
This is needed by the latest gcc, binutils, and gdb, and will avoid using the host's version.
- The version update provides support for Apple Silicon. - The patch offsets were also updated. - The configure command had to be updated to find GMP/MPFR/MPC. The GDB configure script called during build uses different flags to set lib paths.
This adds support for Apple Silicon and zstd.
- This adds support for Apple Silicon hosts. - The patch was renamed (and updated) to reflect the change. - Add zstd support.
- zstd external project requires CMake 3.7, so GIT_SHALLOW can be used unconditionally. - Use `option` to declare OFFLINE. - Expand `OFFLINE` in the ExternalProject calls instead of using an intermediate variable. - Set CMP0135 to NEW.
Binutils 2.41 requires a version newer than what is provided by macOS.
Also run autoreconf to fix a sporadic issue with automake.
Use the github URL as it will not change when the next version releases.
Fixes building with Xcode 16.
Port the following commits: bminor/binutils-gdb@7ae9ecf bminor/binutils-gdb@8170efa
saghul
force-pushed
the
macos-aarch64-toolchain
branch
from
b383500 to
3de3ffb
Compare
Princess-of-Sleeping
requested review from
Princess-of-Sleeping and
d3m3vilurr
|
First, this PR has a change in CMakeLists.txt that updates the gcc version to 13, but the current buildscript kept gcc 10 for some reason. Right @d3m3vilurr? |
|
Thanks for the reply! The main reason to update to 13 is that no prior versions supported Apple Silicon AFAIK. |
couple years ago, we received reports that some built results with newer gcc were broken. after that, we didn't check it yet :'( PS. in my memory(not clear), current gcc version(>=14) has backward compatibility problem between old versions (<14) |
|
Looks cool, I hope it can be merged one day. |
|
@saghul Could you scope the gcc 13 upgrade to macOS Silicon only? And keep gcc 10 for the rest. This should allow to merge it as currently macOS Silicon is not even supported, so worse case it's still not supported. Just want to make sure we don't break the rest for now. |
|
You mean to only bump gcc for macOS but keep the current version for other platforms? I could try that. |
|
@saghul For macOS Silicon (not Intel) 👍 |
|
Ok I'll give that a try. |
Well, back when I opened my PR, I'm pretty sure I went with GCC 13 because it was the latest and With some tinkering, I got GCC 10.5.0 to build on my M1 mac targeting |
|
@saghul Any updates? |
6 participants
This is basically #128 (thanks @FtZPetruska !) with a couple of extra commits to make it work with Xcode 16 and Python 3.13, as I mentioned here.
newlib master has been fixed too so it builds correctly now.
A simple hello world app works, but I'm just getting my feet wet with Vita development, so some extra eyes would be appreciated.
Based on the master commit history... @Princess-of-Sleeping any chance of seeing this landed?
PS: If you'd like to trust some random person's toolchain build, here is mine: https://cloud.saghul.net/s/jFbqQqoKqECHBm9
PPS: Alternatively you can download the toolchain built by the CI: https://github.com/saghul/vita-buildscripts/actions/runs/12926107705
Cheers!