oot-vc

A work-in-progress decompilation of the N64 emulator used in the Wii Virtual Console releases of N64 games like The Legend of Zelda: Ocarina of Time.

Supported versions:

• sm64-j: Super Mario 64 (Wii Virtual Console) - Japan
• sm64-u: Super Mario 64 (Wii Virtual Console) - North America
• sm64-e: Super Mario 64 (Wii Virtual Console) - Europe/Australia
• mk64-j: Mario Kart 64 (Wii Virtual Console) - Japan
• mk64-u: Mario Kart 64 (Wii Virtual Console) - North America
• mk64-e: Mario Kart 64 (Wii Virtual Console) - Europe/Australia
• oot-j: The Legend of Zelda: Ocarina of Time (Wii Virtual Console) - Japan
• oot-u: The Legend of Zelda: Ocarina of Time (Wii Virtual Console) - North America
• oot-e: The Legend of Zelda: Ocarina of Time (Wii Virtual Console) - Europe/Australia

Currently the decompilation mainly targets the oot-j version.

Building

Requirements

You will need the following dependencies:

• git
• ninja
• python3
• wine (for macOS or non-x86 Linux)
• clang-format (optional)

Ubuntu/Debian/Windows (WSL)

You can install the dependencies with the following commands:

sudo apt-get update
sudo apt-get install git ninja-build python3

macOS

You can install dependencies via Homebrew with the following command:

brew install git ninja python3
brew install --cask --no-quarantine gcenx/wine/wine-crossover

Windows (Native)

You will need the following dependencies:

• ninja.exe
• Python (make sure to add it to your PATH during the installation)
• Git for Windows

You need to add C:\Program Files\Git\bin to your system's PATH (not the user one) in order to execute bash scripts properly.

To get objdiff to work properly you also need to add the path to the folder containing ninja.exe to the system's PATH.

Instructions

1. Clone the repo using git clone https://github.com/zeldaret/oot-vc.

2. Extract the following binary containing the N64 emulator from the wad of the version you want to build:

• content1.app

Then, copy the app file and place it in the repo as orig/<version>/content1.app.

You can use gzinject to perform both of this extraction step.

3. Run python3 configure.py to generate the build. (Note: on Windows you might need to run python configure.py.)

4. Run ninja to build the oot-j version, or run ninja <version> to build another version.

Development Tools

Scripts

• ./dol-diff <version> will run dtk dol diff to show the first differing symbol if the build does not match.
• ./dol-apply <version> will run dtk dol apply to sync symbols (e.g. if a function was renamed in the repo).
• ./format will format all source files with clang-format.

objdiff

For local decompilation testing, start the objdiff GUI and open this directory as the project directory. Currently objdiff may not work properly on files using asm-processor (i.e. files with asm_processor=True in configure.py).

asm-differ (diff.py)

First, copy a matching build to the expected/ directory to diff against:

mkdir expected
cp -r build expected/

Then run e.g. ./diff.py -mwo3 xlMain to diff a function for oot-j, or e.g. ./diff.py -mwo3 xlMain -v VERSION to diff a function for another version.

decomp.me

Run tools/decompme.py <c-file> <asm-file> (e.g. tools/decompme.py src/emulator/cpu.c asm/non_matchings/cpu/cpuExecute.s) to create a decomp.me scratch for a function. The C file and all of its included headers will be used as the context.

Permuter

To import a function for decomp-permuter, ensure powerpc-eabi-objdump binary is on your PATH (for instance by adding tools/binutils from this project) and run something like

path/to/permuter/import.py src/emulator/cpu.c asm/non_matchings/cpu/cpuExecute.s
path/to/permuter/permuter.py nonmatchings/cpuExecute -j 8

Sometimes you may need to tweak the source in order for things to import correctly, for example by explicitly marking auto-inlined functions as inline.