This is a captured screenshot from the official OGRE Demos pack, from "Ocean Shader Effects" benchmark. Rendering options: 1600*1200 pixel resolution, Direct3D9 renderer, 4th level of FSAA and 32-bit color depth. In this test by means of the several menus loca Image by OGRE developers; screenshot was captured by me, neD80, via Wikimedia Commons (LGPL).

edge

GAME BOY EMULATOR

edge

Edge — reported as a C++ Game Boy emulator for macOS and iOS with a Time Travel (rewind) feature. The primary repository at github.com/elp2/edge could not be accessed during verification, so implementation details below are cautious and should be confirmed against the project itself.

Jump to download ↓Jump to setup guide ↓

Game BoyPRIMARY SYSTEM

History documentedPROJECT BEGAN

Open source (reported)PROJECT MODEL

WHY IT MATTERS

Why this project matters

Emulators that target Apple platforms and expose macOS/iOS frontends with time-travel/rewind features are useful for developers, TASers and players who want integrated platform UX (native controls, system audio, windowing and continuity with iOS). Edge is presented as one such project focused on the Game Boy line.

BEST FOR

Best known strengths

Native macOS/iOS focus (reported), C++ implementation (familiar toolchain for contributors), and a Time Travel (rewind) feature mentioned in the project description — useful for rapid debugging and gameplay rewinding if implemented.

Gameplay from Tetris on Game Boy.

The people behind edge

History and verification notes

The user-supplied repository address is https://github.com/elp2/edge. I attempted to access the GitHub repository and related project pages during research but received a network restriction (HTTP 429 Too Many Requests) when opening that URL, preventing direct verification of repository contents, releases, or documentation. Because the official repository could not be inspected, the statements above come from the project's short description provided by the user; they have not been confirmed against the repository's README, release notes, or source files. I consulted other contemporary macOS/iOS Game Boy emulator projects during research to understand typical feature sets (examples include SameBoy and several active macOS/iOS frontends), but those are separate projects and not sources for Edge-specific implementation details. If you want a fully verified profile, please either allow me to re-check the GitHub URL now (I will retry) or paste the repository README or relevant files (README, INSTALL, CMakeLists.txt, Xcode project) here.

What edge supports

Game Boy (DMG) — reported
Game Boy Color (CGB) — reported
macOS — reported
iOS — reported

Download and availability

OFFICIAL DOWNLOADS

Get edge

Reported releases are hosted on the project's GitHub releases page (user-provided: https://github.com/elp2/edge/releases). I could not retrieve release files during verification due to a GitHub access error; confirm the latest release there and download source archives or binary packages from the official releases page.

Get edge ↗

DOCUMENTATION

Official documentation

Read the official configuration, compatibility, and troubleshooting material before changing advanced options.

Read official documentation ↗

Broken or missing download? Emulator projects move and official links sometimes change. Please contact Retro Replay so the source can be verified and updated.

edge setup guide

Setup note: The following setup guide is a careful, conservative walkthrough for building and running a C++ macOS/iOS Game Boy emulator project. It uses general, verifiable steps common to open-source C++ emulators and macOS/iOS projects. Because I could not verify the repository contents directly, treat these steps as a practical checklist; consult the project's README or INSTALL files (or provide them to me) for exact commands, dependency names, and build targets.

1) Acquire the source: Clone the repository (or download the source tarball/zip from GitHub releases). Example: git clone https://github.com/elp2/edge.git. If you download a release archive, extract it into a folder and open that folder in Terminal or Finder.
2) Read the repository docs: Open README.md, INSTALL.md, or docs/ in the project root. These files usually list required third-party libraries, supported platforms, build systems (CMake, Xcode project, Makefile), and any special steps for iOS signing or macOS sandboxing. If the repository contains a LICENSE file, review it for redistribution and contribution terms.
3) Install toolchain and dependencies (macOS): Install Xcode from the App Store (for iOS/macOS SDKs and Xcode command-line tools) and then install the Xcode command-line tools (xcode-select –install). If the project uses CMake, also install CMake (via Homebrew: brew install cmake). Additional libraries commonly required by emulators include SDL2 (for cross-platform input/audio/video), libsndfile or portaudio (audio), and optionally fmt/spdlog or Boost for utility code; the actual repo's docs will list exact dependencies.
4) Configure and build (CMake-style): If the repository uses CMake: from the project root create a build directory (mkdir build && cd build). Run cmake .. -DCMAKE_BUILD_TYPE=Release (add -G Xcode if an Xcode project is desired: cmake .. -G Xcode). Then build with cmake –build . –config Release or open the generated .xcodeproj / .xcworkspace in Xcode and build there. For direct Xcode projects, open the project file and select the target (macOS or an iOS simulator/device) then build and run.
5) iOS-specific notes: To run on an iOS device you will need a valid Apple developer provisioning profile and code signing identity configured in Xcode. For simulator targets, an iOS simulator build is usually selectable in Xcode without signing. The repository may include separate targets or conditional compilation flags for iOS (check README/CMakeLists).
6) Required ROMs, BIOS and legal notes: Commercial games, firmware, BIOS files, and copyrighted ROM images are not included in open-source emulator distributions. Use only legally obtained ROMs you own. If the project requires a BIOS/firmware file, its README will say so and specify expected filename and placement; do not assume any BIOS is bundled.
7) Running, saves, and Time Travel (rewind): If the project implements save states and a Time Travel/rewind feature, README or in-app menus should document save-state keybindings and any persistent save file locations (common locations: inside the app support directory on macOS or app container on iOS). Rewind typically requires periodic state snapshots; check config options for maximum rewind duration and memory usage.
8) Controls, input, and controllers: macOS builds typically support keyboard and gamepad input via SDL or native GameController framework. iOS builds commonly map on-screen touch controls or MFi/compatible controllers via GameController. The README or the app’s settings should list the input mappings and how to remap them.

Software reminder: Before building, consult the repository’s README and any platform-specific build notes. If the repo requires third-party libraries, prefer the versions listed there. If you want, provide the repository README or allow me to retry accessing the GitHub URL and I will produce a fully verified, exact setup guide with exact commands and file paths.