Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Methanoid

macrumors regular
Original poster
Jan 6, 2009
110
86
Some older users may recall Universal binaries from PPC days... and with programs like XSlimmer you could strip out the bits you didnt need (so a PPC owner could strip x86 code out or vice versa)...

Is there anything for Apple Silicon to strip out x86 code from Universal 2 binaries? Or some reason why it cannot be done.

Just curious. Don't have an M1 Mac (yet)
 
I saw the difference for Chrome for Intel (100mb) vs for M1 (170mb)... This second bout of Universal Binary crap is going to suck.
 
Some older users may recall Universal binaries from PPC days... and with programs like XSlimmer you could strip out the bits you didnt need (so a PPC owner could strip x86 code out or vice versa)...

Is there anything for Apple Silicon to strip out x86 code from Universal 2 binaries? Or some reason why it cannot be done.

Just curious. Don't have an M1 Mac (yet)
I don't think any third-party app could do that now. You aren't just allowed to change binaries inside of signed apps. There is a command line tool called lipo that can remove unused architectures but if it isn't your app then I don't think there is any way to sign it to work.
 
I don't think any third-party app could do that now. You aren't just allowed to change binaries inside of signed apps. There is a command line tool called lipo that can remove unused architectures but if it isn't your app then I don't think there is any way to sign it to work.

This is almost certainly the case. It won't be readily possible, the app developer would have to enable it as an in-app option (or just offer two separate downloads.)
 
I asked this in a separate post. Monolingual does this (remove architectures) along with extraneous languages. I haven’t tried it on my M1. Keep forgetting to email the developer.
 
  • Like
Reactions: Methanoid
From Monolingual Github "It requires a 64-bit capable Intel-based Mac and at least macOS 10.13 (High Sierra)."

I wonder if it does require Intel CPU and whether it even runs on M1. Still curious about removing bloat and still have not bought an M1 Mac
 
From Monolingual Github "It requires a 64-bit capable Intel-based Mac and at least macOS 10.13 (High Sierra)."

I wonder if it does require Intel CPU and whether it even runs on M1. Still curious about removing bloat and still have not bought an M1 Mac
As I understand it, Monolingual removes language resources (as the name implies), and doesn't do anything to architectures.
Monolingual on GitHub
Developer issue blog
I stand corrected. Actually using the program revealed the following dialog window:
Languages/Architectures selector
 
  • Like
Reactions: msephton
From Monolingual Github "It requires a 64-bit capable Intel-based Mac and at least macOS 10.13 (High Sierra)."

I wonder if it does require Intel CPU and whether it even runs on M1. Still curious about removing bloat and still have not bought an M1 Mac
The latest release, 1.8.2, was released on 2/9/19 and is not M1-compatible.
However, there is a reference to a v. 1.9.0 with M1 compatibility here:
Bump version to 1.9.0
 
Thanks.. now... I wonder what stripping Intel code from AppleSilicon saves on a new install of BigSur? ;-)
 
Thanks.. now... I wonder what stripping Intel code from AppleSilicon saves on a new install of BigSur? ;-)
Well, if every app has 40% extra size to allow for a second architecture, then potentially quite a bit! Fingers crossed for a fruitful new version of Monolingual that knows its way around the new file system.
 
Wouldn't the installer of either the OS or the app simply install the components necessary for the current architecture? The only thing that should be bloated by dual architectures is the installer, not the end result. If the installer doesn't do this, then why bother even using and installer?
 
Wouldn't the installer of either the OS or the app simply install the components necessary for the current architecture? The only thing that should be bloated by dual architectures is the installer, not the end result. If the installer doesn't do this, then why bother even using and installer?
I'd say at least 50% of Mac Apps I encounter don't come with a real installer but just a .app that I am supposed to drag to the Applications folder with the help of some creative graphics.
 
  • Like
Reactions: scottperezfox
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.