mirror of https://github.com/zeldaret/mm.git
Updated Installation (markdown)
parent
ba61988c82
commit
ac8c2c37b5
|
@ -49,15 +49,6 @@ Make a fork of the main repository https://github.com/zeldaret/mm.git and clone
|
|||
|
||||
## Step 6:
|
||||
|
||||
Navigate to the folder you just cloned. Type the following commands:
|
||||
|
||||
```
|
||||
git submodule update --init --recursive
|
||||
pip3 install -r requirements.txt
|
||||
```
|
||||
|
||||
## Step 7:
|
||||
|
||||
You will need to acquire a copy of the ROM. The md5 of this ROM should be `2a0a8acb61538235bc1094d297fb6556`.
|
||||
|
||||
Once this has been done, type, replacing `<ROM>` with the name of your ROM:
|
||||
|
@ -74,22 +65,12 @@ make init
|
|||
|
||||
This will create the build folders as well as a newly created asm folder containing the disassemblies of nearly all the files containing code.
|
||||
|
||||
## Step 8:
|
||||
|
||||
Type the following:
|
||||
```
|
||||
make
|
||||
```
|
||||
|
||||
If all goes well, a ROM rom.z64 should be built and the following text should be printed:
|
||||
|
||||
`rom.z64: OK `
|
||||
|
||||
This make target will also build the ROM. You should see the following text printed: `rom.z64: OK `
|
||||
If you instead see the following:
|
||||
|
||||
```
|
||||
rom.z64: FAILED
|
||||
md5sum: WARNING: 1 computed checksum did NOT match
|
||||
```
|
||||
This means that something is wrong with the ROM's contents. Either the baserom files are incorrect due to a bad ROM, or some piece of code is not matching.
|
||||
|
||||
This means that something is wrong with the ROM's contents. Either the baserom files are incorrect due to a bad ROM, or some piece of code is not matching.
|
||||
The `make init` target will also copy the successful build to the `./expected` directory which will be used by the diff script.
|
Loading…
Reference in New Issue