From 93e00e8dfed2b60bddbac7cc7f8de29272c0b666 Mon Sep 17 00:00:00 2001 From: David Benepe Date: Wed, 27 May 2020 19:37:36 -0500 Subject: [PATCH] Fixed setup section with newlines --- README.md | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/README.md b/README.md index e0f17389..bc5f4205 100644 --- a/README.md +++ b/README.md @@ -8,19 +8,19 @@ Currently, only the US 1.0 version of the game is supported. US 1.1, EU 1.0, EU ## Setup -1. Place the ROM file within the `baseroms` directory. - **a.** Any DKR ROM should work as long as it is US 1.0. - **b.** The name of the ROM file does not matter. It will be detected automatically from an md5 checksum. - **c.** If you use a byte-swapped or little-endian ROM, then it will automatically be converted to a big-endian (.z64) ROM file. -2. Install the latest version of python 3 and binutils. - **a.** Arch users should install: `mips64-elf-binutils` - **b.** Ubuntu/Debian users should install: `binutils-mips-linux-gnu` - **c.** RHEL/CentOS/Fedora users should install: `gcc-mips64-linux-gnu` -3. Finally, run `./setup.sh` in the main directory - **a.** All of the tools within `/tools/` will be built. - **b.** Assets from the original DKR rom will be extracted into the generated `/assets/` folder. - **c.** Lastly, the linker file `dkr.ld` will be generated - +1. Place the ROM file within the `baseroms` directory. + **a.** Any DKR ROM should work as long as it is US 1.0. + **b.** The name of the ROM file does not matter. It will be detected automatically from an md5 checksum. + **c.** If you use a byte-swapped or little-endian ROM, then it will automatically be converted to a big-endian (.z64) ROM file. +2. Install the latest version of python 3 and binutils. + **a.** Arch users should install: `mips64-elf-binutils` + **b.** Ubuntu/Debian users should install: `binutils-mips-linux-gnu` + **c.** RHEL/CentOS/Fedora users should install: `gcc-mips64-linux-gnu` +3. Finally, run `./setup.sh` in the main directory. + **a.** All of the tools within `/tools/` will be built. + **b.** Assets from the original DKR rom will be extracted into the generated `/assets/` folder. + **c.** Lastly, the linker file `dkr.ld` will be generated + If you see the message `Setup complete!`, then you are ready to build. ## Build @@ -43,7 +43,7 @@ This script will generate the linker file `dkr.ld`, which is used for building. This script will extract all the assets from the DKR ROM and place them into `/assets/` folder according to the extract-config file within the `/extract-ver/` folder. You will need to run this every time you update one of the `.extract-config` files. -Note 1: You do not need to call `./generate_ld.sh`, since that is done automatically from this script. +Note 1: You do not need to call `./generate_ld.sh`, since that is done automatically from this script. Note 2: The `/assets/` folder will get deleted if it already exists, so don't put anything important in there! ---