From 14fdc59b5d8d8a0d2a508895d009cd3b6cd71ab2 Mon Sep 17 00:00:00 2001 From: RichardG867 Date: Wed, 20 Apr 2022 23:10:21 -0300 Subject: [PATCH] Clarify macOS app bundle location --- _posts/2022-04-20-86box-v3-4.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2022-04-20-86box-v3-4.md b/_posts/2022-04-20-86box-v3-4.md index 433e9cd..79ce3f9 100644 --- a/_posts/2022-04-20-86box-v3-4.md +++ b/_posts/2022-04-20-86box-v3-4.md @@ -16,7 +16,7 @@ This is the April 2022 update to 86Box, bringing **macOS support**, bugfixes and Continuing on the cross-platform development effort started during [v3.0]({% post_url 2021-12-01-86box-v3-0 %}#linux) and first released for Linux on [v3.2]({% post_url 2022-02-16-86box-v3-2 %}#now-with-linux), we now provide **Intel macOS** builds of 86Box. These should work on macOS High Sierra 10.13 and newer, natively on Intel Macs and through Rosetta 2 on Apple Silicon Macs. [dob205](https://github.com/dob205) was our main macOS tester, while [**jgilje**](https://github.com/jgilje), [**Cacodemon345**](https://github.com/Cacodemon345) and other contributors did the OS integration work. -As with Linux, there is currently no 86Box manager for macOS, but you can manage emulated machines by **making copies** of `86Box.app`; the `roms/` directory (containing the ROM set) must be placed next to the .app ([example](/assets/images/v3.4/roms.png)\), and the emulated machine's files will be saved next to the .app as well. +As with Linux, there is currently no 86Box manager for macOS, but you can manage emulated machines by **making copies** of `86Box.app` on different places (just dragging it to `/Applications` is currently not recommended); the `roms/` directory (containing the ROM set) must be placed next to the .app ([example](/assets/images/v3.4/roms.png)\), and the emulated machine's files will be saved next to the .app as well. ### But where's Apple Silicon?