Skip to content

Latest commit

 

History

History
551 lines (401 loc) · 25.8 KB

INSTALL.md

File metadata and controls

551 lines (401 loc) · 25.8 KB
Raw

Instructions

These instructions explain how to set up the tools required to build pokefirered, which assembles the source files into a ROM.

These instructions come with notes which can be expanded by clicking the "Note..." text. In general, you should not need to open these unless if you get an error or if you need additional clarification.

If you run into trouble, ask for help on Discord or IRC (see README.md).

Windows

Windows has instructions for building with three possible terminals, providing 3 different options in case the user stumbles upon unexpected errors.

Unscientific benchmarks suggest msys2 is 2x slower than WSL1, and Cygwin is 5-6x slower than WSL1.

Note for advanced users: WSL2...

WSL2 is an option and is even faster than WSL1 if files are stored on the WSL2 file system, but some tools may have trouble interacting with the WSL2 file system over the network drive. For example, tools which use Qt versions before 5.15.2 such as porymap may have problems with parsing the \wsl$ network drive path.

All of the Windows instructions assume that the default drive is C:\. If this differs to your actual drive letter, then replace C with the correct drive letter when reading the instructions.

A note of caution: As Windows 7 is officially unsupported by Microsoft and Windows 8 has very little usage, some maintainers are unwilling to maintain the Windows 7/8 instructions. Thus, these instructions may break in the future with fixes taking longer than fixes to the Windows 10 instructions.

Windows 10 (WSL1)

WSL1 is the preferred terminal to build pokefirered. The following instructions will explain how to install WSL1 (referred to interchangeably as WSL).

Installing WSL1

  1. Open Windows Powershell as Administrator, and run the following command (Right Click or Shift+Insert is paste in the Powershell).

    dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart

  2. Once the process finishes, restart your machine.

  3. The next step is to choose and install a Linux distribution from the Microsoft Store. The following instructions will assume Ubuntu as the Linux distribution of choice.

    Note for advanced users...

    You can pick a preferred Linux distribution, but setup instructions may differ. Debian should work with the given instructions, but has not been tested.

  4. Open the Microsoft Store Linux Selection, click Ubuntu, then click Get, which will install the Ubuntu distribution.

    Notes...

    Note 1: If a dialog pops up asking for you to sign into a Microsoft Account, then just close the dialog.
    Note 2: If the link does not work, then open the Microsoft Store manually, and search for the Ubuntu app (choose the one with no version number).

Setting up WSL1

Some tips before proceeding:

  • In WSL, Copy and Paste is either done via
    • right-click (selection + right click to Copy, right click with no selection to Paste)
    • Ctrl+Shift+C/Ctrl+Shift+V (enabled by right-clicking the title bar, going to Properties, then checking the checkbox next to "Use Ctrl+Shift+C/V as Copy/Paste").
  • Some of the commands that you'll run will ask for your WSL password and/or confirmation to perform the stated action. This is to be expected, just enter your WSL password and/or the yes action when necessary.

  1. Open Ubuntu (e.g. using Search).

  2. WSL/Ubuntu will set up its own installation when it runs for the first time. Once WSL/Ubuntu finishes installing, it will ask for a username and password (to be input in).

    Note...

    When typing in the password, there will be no visible response, but the terminal will still read in input.

  3. Update WSL/Ubuntu before continuing. Do this by running the following command. These commands will likely take a long time to finish:

    sudo apt update && sudo apt upgrade

Note: If the repository you plan to build has an older revision of the INSTALL.md, then follow the legacy WSL1 instructions from here.

  1. Certain packages are required to build pokefirered. Install these packages by running the following command:

    sudo apt install build-essential binutils-arm-none-eabi git libpng-dev
    Note...

    If the above command does not work, try the above command but replacing apt with apt-get.

Choosing where to store pokefirered (WSL1)

WSL has its own file system that's not natively accessible from Windows, but Windows files are accessible from WSL. So you're going to want to store pokefirered within Windows.

For example, say you want to store pokefirered (and agbcc) in C:\Users\<user>\Desktop\decomps. First, ensure that the folder already exists. Then, enter this command to change directory to said folder, where <user> is your Windows username:

cd /mnt/c/Users/<user>/Desktop/decomps
Notes...

Note 1: The Windows C:\ drive is called /mnt/c/ in WSL.
Note 2: If the path has spaces, then the path must be wrapped with quotations, e.g. cd "/mnt/c/users/<user>/Desktop/decomp folder".
Note 3: Windows path names are case-insensitive so adhering to capitalization isn't needed

If this works, then proceed to Installation.

Otherwise, ask for help on Discord or IRC (see README.md), or continue reading below for Windows instructions using msys2.

Windows (msys2)

Installing devkitARM

  1. Download the devkitPro installer here.
  2. Run the devkitPro installer. In the "Choose Components" screen, uncheck everything except GBA Development unless if you plan to install other devkitPro components for other purposes. Keep the install location as C:\devkitPro and leave the Start Menu option unchanged.

Setting up msys2

Note that in msys2, Copy is Ctrl+Insert and Paste is Shift+Insert.

  1. Open msys2 at C:\devkitPro\msys2\mingw64.exe or run C:\devkitPro\msys2\msys2_shell.bat -mingw64.

  2. Certain packages are required to build pokefirered. Install these by running the following command:

    pacman -S make zlib-devel git mingw-w64-x86_64-gcc mingw-w64-x86_64-libpng
    Note...

    This command will ask for confirmation, just enter the yes action when prompted.

Choosing where to store pokefirered (msys2)

At this point, you can choose a folder to store pokefirered into. If you're okay with storing pokefirered in the user profile folder, then proceed to Installation. Otherwise, you'll need to account for where pokefirered is stored when changing directory to the pokefirered folder.

For example, if you want to store pokefirered (and agbcc) in C:\Users\<user>\Desktop\decomps (where <user> is your Windows username), enter this command:

cd Desktop/decomps

If this works, then proceed to Installation.

Otherwise, ask for help on Discord or IRC (see README.md), or continue reading below for Windows instructions using Cygwin.

Windows (Cygwin)

  1. If devkitARM is not installed, then follow the instructions used to install devkitARM for the msys2 setup before continuing. Remember to not continue following the msys2 instructions by mistake!

Installing Cygwin

  1. Download Cygwin: setup-x86_64.exe for 64-bit Windows, setup-x86.exe for 32-bit.

  2. Run the Cygwin setup. Within the Cygwin setup, leave the default settings until the "Choose A Download Site" screen.

  3. At "Choose a Download Site", select any mirror within the Available Download Sites.

  4. At "Select Packages", set the view to "Full" (top left) and search for the following packages:

    • make
    • git
    • gcc-core
    • gcc-g++
    • libpng-devel

    To quickly find these, use the search bar and type the name of each package. Ensure that the selected package name is the exact same as the one you're trying to download, e.g. cmake is NOT the same as make.

  5. For each package, double click on the text that says "Skip" next to each package to select the most recent version to install. If the text says anything other than "Skip", (e.g. Keep or a version number), then the package is or will be installed and you don't need to do anything.

  6. Once all required packages have been selected, finish the installation.

Configuring devkitARM for Cygwin

Note that in Cygwin, Copy is Ctrl+Insert and Paste is Shift+Insert.

  1. Open Cygwin.

  2. Run the following commands to configure devkitPro to work with Cygwin.

    export DEVKITPRO=/cygdrive/c/devkitpro
echo export DEVKITPRO=$DEVKITPRO >> ~/.bashrc
export DEVKITARM=$DEVKITPRO/devkitARM
echo export DEVKITARM=$DEVKITARM >> ~/.bashrc
    Note...

    Replace the drive letter c with the actual drive letter if it is not c.

Choosing where to store pokefirered (Cygwin)

Cygwin has its own file system that's within Windows, at C:\cygwin64\home\<user>. If you don't want to store pokefirered there, you'll need to account for where pokefirered is stored when changing directory to the pokefirered folder.

For example, if you want to store pokefirered (and agbcc) in C:\Users\<user>\Desktop\decomps, enter this command, where <user> is your Windows username:

cd c:/Users/<user>/Desktop/decomps

Note that the directory must exist in Windows. If you want to store pokefirered in a dedicated folder that doesn't exist (e.g. the example provided above), then create the folder (e.g. using Windows Explorer) before executing the cd command.

Notes...

Note 1: If the path has spaces, then the path must be wrapped with quotations, e.g. cd "c:/users/<user>/Desktop/decomp folder".
Note 2: Windows path names are case-insensitive so adhering to capitalization isn't needed

If this works, then proceed to Installation. Otherwise, ask for help on Discord or IRC (see README.md).

macOS

  1. If the Xcode Command Line Tools are not installed, download the tools here, open your Terminal, and run the following command:

    xcode-select --install

Installing libpng (macOS)

Note for advanced users...

This guide installs libpng via Homebrew as it is the easiest method, however advanced users can install libpng through other means if they so desire.

  1. Open the Terminal.

  2. If Homebrew is not installed, then install Homebrew by following the instructions on the website.

  3. Run the following command to install libpng.

    brew install libpng

    libpng is now installed.

    Continue to Installing devkitARM (macOS) if devkitARM is not installed, otherwise, go to Choosing where to store pokefirered (macOS).

Installing devkitARM (macOS)

  1. Download the devkitpro-pacman-installer.pkg package from here.

  2. Open the package to install devkitPro pacman.

  3. In the Terminal, run the following commands to install devkitARM:

    sudo dkp-pacman -Sy
sudo dkp-pacman -S gba-dev
sudo dkp-pacman -S devkitarm-rules

    The command with gba-dev will ask for the selection of packages to install. Just press Enter to install all of them, followed by entering Y to proceed with the installation.

  4. After the tools are installed, devkitARM must now be made accessible from anywhere by the system. To do so, run the following commands:

    export DEVKITPRO=/opt/devkitpro
echo "export DEVKITPRO=$DEVKITPRO" >> ~/.bashrc
export DEVKITARM=$DEVKITPRO/devkitARM
echo "export DEVKITARM=$DEVKITARM" >> ~/.bashrc

echo "if [ -f ~/.bashrc ]; then . ~/.bashrc; fi" >> ~/.bash_profile

Choosing where to store pokefirered (macOS)

At this point, you can choose a folder to store pokefirered into. If you're okay with storing pokefirered in the user folder, then proceed to Installation. Otherwise, you'll need to account for where pokefirered is stored when changing directory to the pokefirered folder.

For example, if you want to store pokefirered (and agbcc) in ~/Desktop/decomps, enter this command to change directory to the desired folder:

cd Desktop/decomps

Note that the directory must exist in the folder system. If you want to store pokefirered in a dedicated folder that doesn't exist (e.g. the example provided above), then create the folder (e.g. using Finder) before executing the cd command.

Note...

Note: If the path has spaces, then the path must be wrapped with quotations, e.g. cd "Desktop/decomp folder"

If this works, then proceed to Installation. Otherwise, ask for help on Discord or IRC (see README.md).

Linux

Open Terminal and enter the following commands, depending on which distro you're using.

Debian/Ubuntu-based distributions

Run the following command to install the necessary packages:

sudo apt install build-essential binutils-arm-none-eabi git libpng-dev

Then proceed to Choosing where to store pokefirered (Linux).

Note for legacy repos...

If the repository you plan to build has an older revision of the INSTALL.md, then you will have to install devkitARM. Install all the above packages except binutils-arm-none-eabi, and follow the instructions to install devkitARM on Debian/Ubuntu-based distributions.

Other distributions

(Specific instructions for other distributions would be greatly appreciated!)

  1. Try to find the required software in its repositories:

    • gcc
    • g++
    • make
    • git
    • libpng-dev

  2. Follow the instructions here to install devkitPro pacman. As a reminder, the goal is to configure an existing pacman installation to recognize devkitPro's repositories.

  3. Once devkitPro pacman is configured, run the following commands:

    sudo pacman -Sy
sudo pacman -S gba-dev

    The last command will ask for the selection of packages to install. Just press Enter to install all of them, followed by entering Y to proceed with the installation.

Choosing where to store pokefirered (Linux)

At this point, you can choose a folder to store pokefirered (and agbcc) into. If so, you'll have to account for the modified folder path when changing directory to the pokefirered folder.

If this works, then proceed to Installation. Otherwise, ask for help on Discord or IRC (see README.md).

Installation

Note for Windows users...

Consider adding an exception for the pokefirered and/or decomps folder in Windows Security using these instructions. This prevents Microsoft Defender from scanning them which might improve performance while building.

  1. If pokefirered is not already downloaded (some users may prefer to download pokefirered via a git client like GitHub Desktop), run:

    git clone https://github.com/pret/pokefirered
    Note for WSL1...

    If you get an error stating fatal: could not set 'core.filemode' to 'false', then run the following commands:

    cd
sudo umount /mnt/c
sudo mount -t drvfs C: /mnt/c -o metadata,noatime
cd <folder where pokefirered is to be stored>

    Where <folder where pokefirered is to be stored> is the path of the folder where you chose to store pokefirered. Then run the git clone command again.

  2. Install agbcc into pokefirered. The commands to run depend on certain conditions. You should only follow one of the listed instructions:

  • If agbcc has not been built before in the folder where you chose to store pokefirered, run the following commands to build and install it into pokefirered:

    git clone https://github.com/pret/agbcc
cd agbcc
./build.sh
./install.sh ../pokefirered

  • Otherwise, if agbcc has been built before (e.g. if the git clone above fails), but was last built on a different terminal than the one currently used (only relevant to Windows, e.g. switching from msys2 to WSL1), then run the following commands to build and install it into pokefirered:

    cd agbcc
git clean -fX
./build.sh
./install.sh ../pokefirered

  • Otherwise, if agbcc has been built before on the same terminal, run the following commands to install agbcc into pokefirered:

    cd agbcc
./install.sh ../pokefirered
    Note... 
      > If building agbcc or pokefirered results in an error, try deleting the agbcc folder and re-installing agbcc as if it has not been built before.

  1. Once agbcc is installed, change directory back to the base directory where pokefirered and agbcc are stored:

    cd ..

Now you're ready to build pokefirered

Build pokefirered

If you aren't in the pokefirered directory already, then change directory to the pokefirered folder:

cd pokefirered

To build pokefirered.gba for the first time and confirm it matches the official ROM image (Note: to speed up builds, see Parallel builds):

make compare

If an OK is returned, then the installation went smoothly.

Note for Windows... > If you switched terminals since the last build (e.g. from msys2 to WSL1), you must run `make clean-tools` once before any subsequent `make` commands.

To build pokefirered.gba with your changes:

make

Build pokeleafgreen and REV1

Pokemon FireRed and LeafGreen were both released together. As such, this project is capable of building both ROMs. To do so, simply run

make leafgreen

This project can also build the version 1.1 ROMs of both FireRed and LeafGreen. To build each, run

make firered_rev1  # for FireRed 1.1
make leafgreen_rev1  # for LeafGreen 1.1

Building guidance

Parallel builds

See the GNU docs and this Stack Exchange thread for more information.

To speed up building, first get the value of nproc by running the following command:

nproc

Builds can then be sped up by running the following command:

make -j<output of nproc>

Replace <output of nproc> with the number that the nproc command returned.

nproc is not available on macOS. The alternative is sysctl -n hw.ncpu (relevant Stack Overflow thread).

Debug info

To build pokefirered.elf with enhanced debug info:

make DINFO=1

devkitARM's C compiler

This project supports the arm-none-eabi-gcc compiler included with devkitARM. If devkitARM (a.k.a. gba-dev) has already been installed as part of the platform-specific instructions, simply run:

make modern  # or leafgreen_modern, firered_rev1_modern, leafgreen_rev1_modern

Otherwise, follow the instructions below to install devkitARM.

Installing devkitARM on WSL1

  1. gdebi-core must be installed beforehand in order to install devkitPro pacman (which facilitates the installation of devkitARM). Install this with the following command:

    sudo apt install gdebi-core
    Note...

    If the above command does not work, try the above command but replacing apt with apt-get.

  2. Once gdebi-core is done installing, download the devkitPro pacman package here. The file to download is devkitpro-pacman.amd64.deb.

  3. Change directory to where the package was downloaded. For example, if the package file was saved to C:\Users\<user>\Downloads (the Downloads location for most users), enter this command, where *<user> is your Windows username:

    cd /mnt/c/Users/<user>/Downloads

  4. Once the directory has been changed to the folder containing the devkitPro pacman package, run the following commands to install devkitARM.

    sudo gdebi devkitpro-pacman.amd64.deb
sudo dkp-pacman -Sy
sudo dkp-pacman -S gba-dev

    The last command will ask for the selection of packages to install. Just press Enter to install all of them, followed by entering Y to proceed with the installation.

    Note...

    Note: devkitpro-pacman.amd64.deb is the expected filename of the devkitPro package downloaded (for the first command). If the downloaded package filename differs, then use that filename instead.

  5. Run the following command to set devkitPro related environment variables (alternatively, close and re-open WSL):

    source /etc/profile.d/devkit-env.sh

devkitARM is now installed.

Installing devkitARM on Debian/Ubuntu-based distributions

  1. If gdebi-core is not installed, run the following command:

    sudo apt install gdebi-core

  2. Download the devkitPro pacman package here. The file to download is devkitpro-pacman.amd64.deb.

  3. Change directory to where the package was downloaded. Then, run the following commands to install devkitARM:

    sudo gdebi devkitpro-pacman.amd64.deb
sudo dkp-pacman -Sy
sudo dkp-pacman -S gba-dev

    The last command will ask for the selection of packages to install. Just press Enter to install all of them, followed by entering Y to proceed with the installation.

    Note: devkitpro-pacman.amd64.deb is the expected filename of the devkitPro package downloaded (for the first command). If the downloaded package filename differs, then use that filename instead.

  4. Run the following command to set devkitPro related environment variables (alternatively, close and re-open the Terminal):

    source /etc/profile.d/devkit-env.sh

devkitARM is now installed.

Other toolchains

To build using a toolchain other than devkitARM, override the TOOLCHAIN environment variable with the path to your toolchain, which must contain the subdirectory bin.

make TOOLCHAIN="/path/to/toolchain/here"

The following is an example:

make TOOLCHAIN="/usr/local/arm-none-eabi"

To compile the modern target with this toolchain, the subdirectories lib, include, and arm-none-eabi must also be present.

Useful additional tools