Crates.io | cargo-n64 |
lib.rs | cargo-n64 |
version | 0.2.0 |
source | src |
created_at | 2019-04-11 04:28:56.64577 |
updated_at | 2022-06-16 13:09:47.605846 |
description | Cargo subcommand to build Nintendo 64 ROMs |
homepage | |
repository | https://github.com/rust-console/cargo-n64 |
max_upload_size | |
id | 127155 |
size | 48,605 |
cargo-n64
A cargo
subcommand to build Nintendo 64 ROMs in Rust! 🦀
Requires Rust nightly.
When built from source, cargo
will automatically install the correct version of the nightly compiler, based on the rust-toolchain
file. However you will still need to install the rust-src
component separately. It is recommended that you explicitly install the dependencies with the same versions used in CI, as described below.
Install dependencies:
rustup toolchain install $(cat rust-toolchain)
rustup run $(cat rust-toolchain) -- rustup component add rust-src
Install cargo-n64
from source:
cargo install --path cargo-n64
Install cargo-n64
from crates.io:
cargo install cargo-n64
Nintendo 64 ROMs are flat binaries, and each one is unique. There is no standard format for the binary beyond a simple 64-byte header and a ~4KB bootcode (aka Initial Program Loader 3/IPL3). Everything beyond the first 4KB boundary is MIPS code and whatever data it requires. This is unlike modern application or game development where an operating system has a standard binary format (like ELF, PE, or WASM). In fact, the N64 doesn't even have an operating system! The flat binary in the ROM is the operating system, for all intents and purposes.
This makes it challenging to get started with N64 development, in general. You first have to build an OS from scratch, or use a library like libdragon
or libn64
. Then you need a tool (or two, or three!) to convert the object files from the compiler toolchain into a flat binary, add the header and IPL3, and finally fix the IPL3 checksum. cargo-n64
takes the place of the latter set of tools and plugs in nicely to the Rust/cargo ecosystem.
For copyright purposes, the IPL3 binary is not included in this package. Collecting a working IPL3 binary is left as an exercise for the reader. You will be required to provide the path to your IPL3 with the --ipl3
command line argument, or extract it from an existing ROM with --ipl3-from-rom
.