1
0
Fork 0
mirror of https://github.com/zeldaret/oot.git synced 2024-11-14 13:30:47 +00:00
Decompilation of The Legend of Zelda: Ocarina of Time
Find a file
Tharo aa97586659
[Audio 6/?] Build Soundfonts and the Soundfont Table (#2056)
* [Audio 6/?] Build Soundfonts and the Soundfont Table

* Improve lots of error messages

* First suggested changes

* Make audio build debugging more friendly

Co-authored-by: Dragorn421 <Dragorn421@users.noreply.github.com>

* Some fixes from MM review

* Make soundfont_table.h generation depend on the samplebank xmls since they are read, report from which soundfont the invalid pointer indirect warning originates from

---------

Co-authored-by: Dragorn421 <Dragorn421@users.noreply.github.com>
2024-08-27 21:09:59 -04:00
assets Set up build system and disassembly for ntsc-1.2 (#2021) 2024-08-11 06:20:43 -04:00
baseroms [Audio 6/?] Build Soundfonts and the Soundfont Table (#2056) 2024-08-27 21:09:59 -04:00
data [Audio 6/?] Build Soundfonts and the Soundfont Table (#2056) 2024-08-27 21:09:59 -04:00
docs Add all N64 version defines (#2095) 2024-08-26 11:43:59 -04:00
include [Audio 6/?] Build Soundfonts and the Soundfont Table (#2056) 2024-08-27 21:09:59 -04:00
linker_scripts [Audio 6/?] Build Soundfonts and the Soundfont Table (#2056) 2024-08-27 21:09:59 -04:00
src [Audio 6/?] Build Soundfonts and the Soundfont Table (#2056) 2024-08-27 21:09:59 -04:00
tools [Audio 6/?] Build Soundfonts and the Soundfont Table (#2056) 2024-08-27 21:09:59 -04:00
.clang-format Remove gSystemHeap and use _buffersSegmentEnd instead, make buffer alignments explicit for gcc (#1901) 2024-02-27 19:01:47 -05:00
.clang-tidy Format script improvements and use strict name checks (#1275) 2022-06-20 16:31:53 -04:00
.dockerignore Docker fixes (#1357) 2022-08-28 17:21:22 +02:00
.gitattributes
.gitignore gitignore clangd files (#2086) 2024-08-25 02:31:53 -04:00
diff.py subrepo and update asm-differ (#1664) 2024-01-30 15:25:15 -05:00
diff_settings.py Move roms to build folder (#1651) 2024-02-02 16:34:20 -05:00
docker-compose.yml
Dockerfile Mapfile Parser (#1518) 2023-07-31 22:30:26 -04:00
Doxyfile
extract_assets.py Match NTSC file select (#1998) 2024-08-08 00:27:02 -04:00
first_diff.py Move roms to build folder (#1651) 2024-02-02 16:34:20 -05:00
fixle.sh
format.py Add -DF3DEX_GBI_2 to format.py flags (#2022) 2024-08-09 20:02:30 -04:00
Jenkinsfile Build all GC retail ROMs in Jenkins (#2027) 2024-08-14 23:39:34 -04:00
Makefile [Audio 6/?] Build Soundfonts and the Soundfont Table (#2056) 2024-08-27 21:09:59 -04:00
README.md Update links in readme (#2043) 2024-08-15 16:07:22 -04:00
requirements.txt Add "disasm sym_info.py" script (#2054) 2024-08-19 23:58:41 +02:00
retail_progress.py Set up build system and disassembly for ntsc-1.2 (#2021) 2024-08-11 06:20:43 -04:00
spec [Audio 6/?] Build Soundfonts and the Soundfont Table (#2056) 2024-08-27 21:09:59 -04:00
sym_info.py Move roms to build folder (#1651) 2024-02-02 16:34:20 -05:00
undefined_syms.txt [ntsc-1.2] Partially match z_en_mag (#2079) 2024-08-25 17:57:49 +02:00

The Legend of Zelda: Ocarina of Time

Build Status Decompilation Progress Contributors Discord Channel

- WARNING! -

This repository is a work in progress, and while it can be used to make certain changes, it's still
constantly evolving. If you use it for modding purposes in its current state, please be aware that
the codebase can drastically change at any time. Also note that some parts of the ROM may not be
'shiftable' yet, so modifying them could be difficult at this point.

This is a WIP decompilation of The Legend of Zelda: Ocarina of Time. The purpose of the project is to recreate a source code base for the game from scratch, using information found inside the game along with static and/or dynamic analysis. It is not producing a PC port. For more information you can get in touch with the team on our Discord server.

The only build currently supported is Master Quest (Debug), but other versions are planned to be supported.

It builds the following ROM:

  • oot-gc-eu-mq-dbg.z64 md5: 75e344f41c26ec2ec5ad92caa9e25629

Note: This repository does not include any of the assets necessary to build the ROM. A prior copy of the game is required to extract the needed assets.

Website: https://zelda.deco.mp

Discord: https://discord.zelda.deco.mp

Installation

We recommend using WSL on Windows, or native Linux, which the rest of this readme describes. We currently have instructions for

(These will also depend on the Linux instructions.) Some of these may also be out of date or unmaintained; usually our contributors use WSL, Linux, and macOS, so these instructions should be up to date.

Windows

For Windows 10 or 11, install WSL and a distribution by following this WSL Installation Guide. We recommend using Ubuntu 20.04 as the Linux distribution.

For older versions of Windows, install a Linux VM or refer to Docker instructions.

Linux (Native or under WSL / VM)

1. Install build dependencies

The build process has the following package requirements:

  • git
  • build-essential
  • binutils-mips-linux-gnu
  • python3
  • python3-pip
  • python3-venv
  • libpng-dev
  • libxml2-dev

Under Debian / Ubuntu (which we recommend using), you can install them with the following commands:

sudo apt-get update
sudo apt-get install git build-essential binutils-mips-linux-gnu python3 python3-pip python3-venv libpng-dev libxml2-dev

If you are using GCC as the compiler for Ocarina of Time, you will also need:

  • gcc-mips-linux-gnu

2. Clone the repository

N.B. If using WSL, we strongly encourage you to clone into WSL's Linux filesystem using Linux's git. Cloning into the Windows filesystem will result in much slower read/write speeds, and often causes issues when Windows copies the files with the wrong line endings, which the compiler IDO cannot handle correctly.

Clone https://github.com/zeldaret/oot.git where you wish to have the project, with a command such as:

git clone https://github.com/zeldaret/oot.git

This will copy the GitHub repository contents into a new folder in the current directory called oot. Change into this directory before doing anything else:

cd oot

3. Prepare a base ROM

Place a copy of the Master Quest (Debug) ROM inside the baseroms/gc-eu-mq-dbg/ folder. If you are under WSL, you can run the command explorer.exe . to open the current directory in the Windows file explorer.

Rename the file to baserom.z64, baserom.n64 or baserom.v64, depending on the original extension.

4. Setup the ROM and build process

Setup and extract everything from your ROM with the following command:

make setup

This downloads some dependencies (from pip), and compiles tools for the build process. Then it generates a new ROM baseroms/gc-eu-mq-dbg/baserom-decompressed.z64 that will have the overdump removed and the header patched. It will also extract the individual assets from the ROM.

5. Build the ROM

Run make to build the ROM. Make sure your path to the project is not too long, otherwise this process may error.

make

If all goes well, a new ROM should be built at build/gc-eu-mq-dbg/oot-gc-eu-mq-dbg.z64, and the following text printed:

build/gc-eu-mq-dbg/oot-gc-eu-mq-dbg.z64: OK

If you instead see the following:

build/gc-eu-mq-dbg/oot-gc-eu-mq-dbg.z64: FAILED
md5sum: WARNING: 1 computed checksum did NOT match

This means that the built ROM isn't the same as the base one, so something went wrong or some part of the code doesn't match.

NOTE: to speed up the build, you can either:

  • pass -jN to make setup and make, where N is the number of threads to use in the build. The generally-accepted wisdom is to use the number of virtual cores your computer has.
  • pass -j to make setup and make, to use as many threads as possible, but beware that this can use too much memory on lower-end systems.

Both of these have the disadvantage that the ordering of the terminal output is scrambled, so for debugging it is best to stick to one thread (i.e. not pass -j or -jN).

Contributing

All contributions are welcome. This is a group effort, and even small contributions can make a difference. Some tasks also don't require much knowledge to get started.

Most discussions happen on our Discord Server, where you are welcome to ask if you need help getting started, or if you have any questions regarding this project and other decompilation projects.