Post Go back to editing

LTspice v17.2.4 for macOS is «Apple Silicon default», while LTspice v26 is Intel x86-64 only. WHY?

Thread Summary

The user installed LTspice 26 on a new MacBook M5 and found it required Rosetta2 for x86-64 emulation, unlike the universal binary LTspice 17.2.4. The support engineer confirmed that LTspice 26 is a port of the Windows version using CodeWeavers Crossover, which includes both x86-64 and ARM v8 components, but the simulation core runs under emulation. They are working toward universal support and noted that the current Mac version performs well on Apple Silicon.
AI Generated Content
Category: Software
Product Number: LTspice
Software Version: 17.x vs. 26.x

Got a new MacBook M5. Downloaded latest LTspice 26 for macOS (v26.6.2) and installed.

Only to be greeted with the requirement of first installing Rosetta2 binary translator from Intel x86-64 opcodes into ARM v8 (Apple Silicon M5) opcodes.

Went back to my older MacBook M1 to investigate the LTspice v17.2.4 already installed on that machine, and it listed as 'universal' binary.

In other words both x86-64 and ARM v8 / Apple Silicon, meaning it it is both compiled for, and runs natively on both CPU architectures.

Now, if there is one task I will definitely not run in emulation, it is [spice] simulations. 

Removed LTspice 26 and installed LTspice 17 on my new MacBook M5 as well. LTspice version 17.2.4 runs fine, natively.

What gives? Progress?

  • What gives? Progress?

    Yes, progress. Joking aside, we are working toward universal support. Afraid I don't have a timeline right now. I personally use the latest Mac version of LTspice on my M3 pro, Tahoe, machine and it is quite snappy. 

    mike

  • Had a peek inside that 'LTspice_v26.app' and found CodeWeavers Crossover Bottle configuration, complete with «drive_c/Windows…» and «drive_c/Program Files…» folders. Even Internet Explorer and Media Player are in there. No such baggage in the 'LTspice_v17.app.' 

    Does not exactly inspire confidence. Guess this means LTspice v26 has been 'overhauled' with a 'modern' M$ Windows desktop integration, be it WinUI3, WPF or whatever is in favor nowadays. A front-end that is now entirely emulated on macOS, including the x86-64 ABI. 

    The one remaining question then, is whether the actual LTspice v26 number crunching simulator is also running under a binary emulation? The LTspice v26 app package contains both a 'LTspice' file registering as 'Mach-O 64-bit executable x86_64' and a 'LTspice.exe' file registering as 'PE32+ executable (GUI) x86-64, for MS Windows'. So I guess the answer is yes, it too, runs under binary emulation. 

  • Hi  ,

    Had a peek inside that 'LTspice_v26.app' and found CodeWeavers Crossover Bottle configuration, complete with «drive_c/Windows…» and «drive_c/Program Files…» folders. Even Internet Explorer and Media Player are in there. No such baggage in the 'LTspice_v17.app

    Correct, it is no secret that the current version of LTspice Mac it is a port of the Windows version via Codeweavers. For now, this enables us to keep the mac version in sync with the Windows version while making under-the-hood improvements. We do test the comparative simulation performance of LTspice in various environments, and you might be surprised by the results; emulation is not always bad. Nevertheless, it is non-ideal, but it enables progress. Will porting from Windows be the long-term solution for Mac (or even Linux)? Probably not.

    I've been using Windows LTspice for years now under crossover, on both my I9 mac and M3 mac and it runs just as well as it does on my Win 11 machine. I have two macs running LTspice in both Crossover (many versions in many bottles) as well as running ported LTspice. I run LTspice on one Win 11 machine only when I must test something particular to Windows. You may deduce from this which environment I prefer. If the performance of the Mac port were significantly worse (for being not a mac binary), I would not punish myself by using it.

    mike

Before You Switch


Switching languages will make ADI Explorer unavailable. Resume your session by switching back to English and reopening ADI Explorer.