Native machine debugging on M1

The advantage of running the Xojo IDE on the M1 is that you can debug both an Intel or M1 based app on the same machine. Find the new Architecture settings in the macOS Build Settings inspector. For purposes of macOS builds, x86 64-bit means Intel and ARM 64-bit is M1.

Note that when you debug a Universal app, you will actually be debugging an Intel app on an M1 (at least currently, until we build our Xojo IDE for M1) . In order to debug a native M1 app, choose the ARM 64-bit architecture when debugging.

Remote debugging to M1

If your preference is working on your Intel based Mac, you can also setup Remote Debugging to your M1 machine to debug Intel or M1 based apps. The same architecture settings apply, so to remote debug a native M1 build, select the ARM 64-bit architecture. If you select the x86 64-bit or Universal architecture then you will be debugging an Intel build.

Happy coding & debugging!

Download mp3.

Topics

• Xojo 2020r2 Download
• Xojo 2020r2 Release Notes
• Xojo Team
• Windows & Linux on M1 Macs

If you are new to all this, it is important to understand the parts involved. First there are virtual machines, which act as virtual computers running on a main or host computer. Second, there are the instruction sets for the computer and OS. These virtual computers run an operating system (OS) of some kind and in most cases this OS has to have the same instruction set as the host computer. This allows the instruction to be passed through the VM to the CPU and allows for good performance. Which is what makes it so easy to run Windows 10 x86 on an Intel Mac — they both are using Intel CPUs with the same instruction sets.

But what if the instruction sets differ as they do with Intel and M1 Macs? Obviously you can no longer pass an x86 instruction to an M1 chip and expect anything to happen. So some translation or emulation needs to happen. This is typically much, much slower.

In general this is what Apple is doing with Rosetta 2 on Big Sur to allow your x86 Mac apps to run on an M1 Mac. They do an entire app translation on first launch (and also re-do it at times) and then run the translated app. This is a great technique but it doesn’t really work at a virtual machine level. And in fact, Apple specifically says that Rosetta 2 cannot be used with virtualization software.

That’s the bad news. But there are options on the horizon.

Emulation

The first option is OS-level emulation. What would happen here is that emulation software (say, QEMU, a popular open-source emulator and virtualizer) would translate x86 instructions to ARM instructions (usually on-the-fly) so that an x86 operating system could run on an M1 Mac. In theory this would allow Windows 10 x86 for example to run as a (virtual computer) on an M1 Mac.

Technically this is more than a theory since it has been done before. You may remember it was possible to run Windows 98 x86 on a PowerPC Mac back in the day using software such as Connectix Virtual PC. The downside to this approach is that it can be quite slow. Fortunately the M1 Macs are proving to be very speedy and might be able make this technique acceptable for casual use. I expect the QEMU project will be updated to eventually allow emulation of x86 operating systems on M1 Macs.

OS Vendors

You might remember in the WWDC 2020 keynote Apple showed Linux running as a virtual machine with Parallels on an M1 Mac. This demo was actually running an ARM Linux distro in that virtual machine. Since it was not an x86 distro, its usefulness depends on its ability to run the apps you need. If you wanted to run an x86 Linux app then it would not work on an ARM distro.

However, the OS vendors are working on this. Much like what Apple did with Rosetta 2, they can add OS-level support to translate individual apps from x86 to ARM, thus allowing them to work in a virtual machine. I haven’t heard of progress on this front with Linux, but I expect there will be some convoluted way to do it at some point.

Microsoft does have an ARM version of Windows, but right now it is only licensed for OEM use to include with a computer, so virtualizing it is not yet an option. And even if you could virtualize ARM Windows on your M1 Mac, it also is only useful to you if it can run the apps you want.

Currently ARM Windows has a translator that lets it run 32-bit x86 apps, but performance is poor, especially when compared to what Apple has done with Rosetta 2 in Big Sur. Microsoft has said they are working on adding the ability to run 64-bit x86 apps on ARM Windows, but that feature is not ready yet and performance is unknown.

I expect virtualizers such as Parallels, VMware and VirtualBox will all eventually have versions that run on M1 Macs and can run ARM operating systems, although perhaps just Linux to start. I don’t expect them to include emulators in their products.

Update (2021-4-14): Parallels has just released 16.5 with support for running Windows for ARM on M1 Macs.

When Microsoft adds 64-bit x86 translation and has it working at a decent speed and if it decides to make ARM Windows available for use in virtual machines then you would also be able to run Windows on an M1 Mac and run common Windows apps. But for now, we wait.

Update (2020-12-08): Some progress continues to be made on this. Here are some rough instructions on how to get Windows ARM running in a VM (UTM running on QEMU).

Other Options

Another option is the CodeWeavers product that is based on the WINE open-source project. This project essentially provides a translated Windows API that allows some Windows apps to run on a Mac. It does not run Windows itself, only apps, and only a small subset at that.

But because it translates the apps to essentially a Mac x86 app, they are a candidate for Rosetta 2 on Big Sur to translate. That’s a lot of levels of translation, but in the end you end up with a Windows app running on an M1 Mac.

CodeWeavers recently posted some information about their early testing of this.

Wrap Up

With all this said, if you require the ability to run an x86 version of Windows or Linux, then an M1 Mac cannot be your sole machine at this time. You’ll either want to also have an Intel Mac to run those in virtual machines or get dedicated separate hardware for them.

And if you want to make your own native apps for M1 Macs, Xojo now has the ability to create native apps for M1 Macs.

Xojo 2020 Release 2 is available for download now. Xojo is free to use for learning and development. For information on pricing and licensing options, please visit our store.

Well, not to worry as both Apple and Xojo have your back.

For most people, you actually don’t have to do anything because of an amazing Apple technology called Rosetta 2. Built into Big Sur, Rosetta 2 is a translation technology that automatically converts most x86-64 (Intel 64-bit) app binaries so that they can run on an Apple Silicon Mac. To you and your users, this process is entirely transparent. Most apps won’t even have a noticeable performance difference. Because of Rosetta 2, moving to Apple Silicon Macs will be painless for all.

For the best possible performance you will want to take advantage of another Apple technology called the Universal Binary. A Universal Binary app looks the same as a regular app, but it contains one version of the app that can run on x86-64 (Intel 64-bit) and another that can run on Apple Silicon.

Starting with Xojo 2020 Release 2 (download now!) you’ll be able to build Universal Binary apps! All you’ll have to do is go to your macOS Build Settings and change the Architecture from “x64 (64-bit)” to “Universal” and re-build your project. Xojo does everything else for you.

Note that if you use plugins, you’ll have to get updated plugins that include Apple Silicon components from the plugin author in order to build a Universal Binary.

Yesterday we hit an important milestone, compiling the first native Xojo app for Apple Silicon. There’s more work to do of course, but “Hello World” is a huge step towards bringing you the ability to build your apps for Apple’s future computing platform.