mirror/86box.github.io
1
0
Fork 0
mirror of https://github.com/86Box/86box.github.io.git synced 2026-02-22 01:25:35 -07:00
Code Issues Packages Projects Releases Wiki Activity

Add update about ROM path on AppImage

Browse Source
This commit is contained in:
RichardG867
2022-02-16 20:23:22 -03:00
parent 557e121b5f
commit 71cc97e7b9
2 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
_posts/2022-02-16-86box-v3-2.md
View File

@@ -18,6 +18,12 @@ This Linux version was made possible by the massive work put in by contributors
Linux builds are distributed as [**AppImage**](https://appimage.org) binaries for maximum compatibility. We've tested these on distributions as old as **Ubuntu 16.04** and as new as **Manjaro 21.2.2**, but if you run into issues on your specific distro, [please let us know](/#social). Binaries for **x86_64**, **ARM32** and **ARM64** architectures are available; 32-bit x86 is currently not available due to a [packaging issue](https://github.com/AppImageCrafters/AppRun/issues/37). Of course, building 86Box from source and running it with system libraries is still an option, and there's a [community-maintained Arch Linux AUR package](https://aur.archlinux.org/packages/86box) which does just that.
**IMPORTANT UPDATE:** On Linux, you should place the `roms/` directory (containing the ROM set) in the **same directory** as the `.AppImage` file ([example](/assets/images/v3.2/roms.png)\). A global ROM path and a manager interface will be added in a future release. For now, you can manage emulated machines through one of the following methods:
* Keeping multiple copies (or symlinks) of the 86Box `.AppImage` and the `roms/` directory.
* Running the 86Box `.AppImage` with the `-P /path/to/machine/directory` switch, which **does not require** copying `roms/` over to the emulated machine's directory.
* Running the 86Box `.AppImage` from a different working directory, which also **does not require** copying `roms/` over.
The **Windows version** will remain on the existing Win32 user interface for now, as [**jriwanek**](https://github.com/jriwanek) has stepped up to maintain it, at least while we work on some Windows-specific odds and ends of the Qt interface. All UI points in the changelog below apply to both interfaces.
<hr />