2026-01-15 07:39:59 -07:00
CI
2024-04-09 12:56:06 +03:00
2024-12-17 18:46:20 -07:00
2026-01-07 18:45:47 -07:00
2025-06-27 19:01:14 -07:00
2026-01-15 07:39:59 -07:00
2025-06-03 20:31:44 -07:00
2025-06-27 19:01:14 -07:00
2026-01-15 07:39:59 -07:00
2024-09-15 18:31:36 -07:00
2025-11-29 07:52:41 -07:00
2024-04-15 07:01:51 -07:00
2024-10-06 23:28:05 -07:00
2025-11-29 07:52:41 -07:00
2026-01-15 07:39:59 -07:00

DingusPPC

Written by divingkatae and maximumspatium

Be warned the program is highly unfinished and could use a lot of testing. Any feedback is welcome.

Philosophy of Use

While many other PowerPC emus exist (PearPC, Sheepshaver), none of them currently attempt emulation of PowerPC Macs accurately (except for QEMU).

This program aims to not only improve upon what Sheepshaver, PearPC, and other PowerPC Mac emulators have done, but also to provide a better debugging environment. This currently is designed to work best with PowerPC NuBus and Old World ROMs, including those of the Power Mac 6100, 7200, and G3 Beige.

Implemented Features

Several machines have been implemented to varying degrees, like many Old World PowerPC Macs, early New World PowerPC Macs, and the Pippin.

This emulator has a debugging environment, complete with a disassembler.

How to Use

This program currently uses the command prompt to work.

There are a few command line arguments one can enter when starting the program.

-r, --realtime

Run the emulator in runtime.

-d, --debugger

Enter the interactive debugger.

-b, --bootrom TEXT:FILE

Specifies the Boot ROM path. It otherwise looks for bootrom.bin.

-m, --machine TEXT

Specify machine ID. Otherwise, the emulator will attempt to determine machine ID from the boot rom otherwise.

As of now, the most complete machines are the Power Mac 6100, the Power Mac 7500, and the Power Mac G3 Beige.

To go into to the debugger regardless of how you started the emulator, press Control and C on the terminal window.

How to Compile

You need to install development tools first.

At minimum, a C++20 compliant compiler and CMake are required.

Clone the repository using the appropriate command:

git clone https://github.com/dingusdev/dingusppc

If this is from a mirror, replace the argument with the source you want to use instead.

You will also have to recursive clone or run

git submodule update --init --recursive

This is because the CubeB, Capstone, and SDL2 modules are not included by default.

For SDL2, Linux users may also have to run:

sudo apt install libsdl2-dev

CLI11 and loguru are already included in the thirdparty folder and compiled along with the rest of DingusPPC.

For example, to build the project in a Unix-like environment, you will need to run the following commands in the OS terminal:

mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
make dingusppc

You may specify another build type using the variable CMAKE_BUILD_TYPE.

For Raspbian, you may also need the following command:

sudo apt install doxygen graphviz

Testing

DingusPPC includes a test suite for verifying the correctness of its PowerPC CPU emulation. To build the tests, use the following terminal commands:

mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release -DDPPC_BUILD_PPC_TESTS=True ..
make testppc

Intended Minimum Requirements

  • Windows 7 or newer (64-bit), Linux 4.4 or newer, Mac OS X 10.9 or newer (64-bit)
  • Intel Core 2 Duo or better
  • 2 GB of RAM
  • 2 GB of Hard Disk Space
  • Graphics Card with a minimum resolution of 800*600
Languages
C++ 93.9%
C 4%
Python 1.2%
CMake 0.8%
Objective-C 0.1%