-
+
Jump/Branch/Function- Tells the cpu to execute instructions somewhere else and come back here when done.Hexadecimal- A numbering system just like decimal (also called base-ten) or roman numerals. An easy method for programmers and computers to understand each other which groups/separates bytes of information in a readable format. Representing information as decimal results in an unreadable mess.s32/word/int- A max size for a number. Data represented as 32 bits or 4 bytes:0x00000001. It consists of eight digits.s16/half-word/short- A number represented as 16 bits or 2 bytes:0x0001. It consists of four digits. Maximum value 65,535 (0xFFFF).s8/byte/char- A number represented as 8 bits or 1 byte:0x01. It consists of two digits. Maximum value 255 (0xFF).- Generated by
1.9.1
+Definitions
+-Addresses
++Addresses
Computers use addresses to jump through code. This works similar to finding a house using its address. Except, that reaching the house is nearly instantaneous and it only contains more instructions and jumps or some data such as a texture or a text string. Also, when finished with the house, you travel back to the previous destination which may have some left-over instructions or more jumps. You can imagine this quickly becoming a spaghetti monster jumping all over the place.
A typical N64 address: 0x8029E158
In an N64 program, addresses begin at 0x80000000. As you create code, data, and the like, the compiler will add onto this base number and assign variables to an address.
You might expect to see this: 000300000005 or 0x0003 0x00000005 But actually, it will be this:
This is called alignment. The compiler aligned b to the next 'major' address. Of course, if you program two s16's then the blank 0x0000 will be used. The max size of an s8 is 0xFF (255). Trying to write a number higher than 255 to an s8 type may crash the program as it might try to write onto the next variable.
-Code
++Code
Code contains addresses too. Lets take a look at some example assembly:
-
+
This method is not recommended nor supported. However, it is the only solution to build in W7/W8. WSL is the path of least resistance, use that not this
++Compiling mk64 Decomp In Windows
+This method is not recommended nor supported. However, it is the only solution to build in W7/W8. WSL is the path of least resistance, use that not this
Building decomp using msys on Windows is a journey.. A journey akin to crawling over broken glass in the dark.
- leogames
The extraneous and convoluted process to building mk64 decomp on Windows begins with disabling your anti-virus program or adding an exception to the mk64 decomp folder and the msys2 installation folder. Please note that this action may impact the security of your system. Prior to proceeding, make sure to understand the increased security risks that may result from this step. Nobody except you, is responsible and liable for your system and its security.
--Preamble
++Preamble
Any misteps may require a complete uninstall of MSYS2 MinGW x64 and restarting from the very beginning.
It is unknown if MSYS MinGW x32 is supported (most likely not).
-Step 1: Download MSYS2 MinGW x64
++Step 1: Download MSYS2 MinGW x64
Follow the initial instructions to update the base packages. Ignore installing any extra packages in-case they conflict with the below steps.
MinGW is a separate program from Msys2. However, it must be wrapped right into msys2. Compiling recomp requires steps using
MSYS2 MSYS and MSYS2 MinGW x64. The instructions will clearly differentiate which terminal program to launch and run in the section titles.
-<em>Why flip-flop between both?</em>
+Why flip-flop between both?
Compiling the recomp executable that generates the source files for compiling the compiler requires capstone. A disassembly, analysis, and reverse-engineering framework. Capstone is only available on MSYS2 MinGW x64. It is not available on MSYS2 MSYS. However, compiling the compiler itself requires MSYS2 MSYS because it contains an equivallent dependency for mman. A memory mapping library. MSYS2 MinGW x64 does not contain an equivallent dependancy.
-Step 2: Install Dependancies in MSYS2 MinGW x64
++Step 2: Install Dependancies in MSYS2 MinGW x64
-Step 3: Install Dependencies in MSYS2 MSYS
++Step 3: Install Dependencies in MSYS2 MSYS
-Step 3.5: Rename include in recomp.cpp
++Step 3.5: Rename include in recomp.cpp
For some reason on Windows capstone is inside of a capstone folder.
-Step 4: Get Binutils
++Step 4: Get Binutils
Download and install the mips64 tool chain:
https://github.com/N64-tools/mips64-gcc-toolchain
Merge the inner folders (bin, share, etc.) with the respective folders in C:\msys64\mingw64\
-Step 5: Compiling recomp.exe in <tt>MSYS2 MinGW x64</tt>
++Step 5: Compiling recomp.exe in <tt>MSYS2 MinGW x64</tt>
In MSYS2 MinGW x64 run in mk64/tools/ido5.3_recomp/:
-Step 6: Generate Recomp Source Files in <tt>MSYS2 MinGW x64</tt>
++Step 6: Generate Recomp Source Files in <tt>MSYS2 MinGW x64</tt>
Generate the .c files which will compile into the recomp binaries. mk64 requires the following compiler binaries: as1, cc, cfe, copt, ugen, ujoin, uld, umerge, uopt
In MSYS2 MinGW x64 run in the directory mk64/tools/ido5.3_recomp/:
If you get an assertion failed error. Then the directory to the compiler is incorrect. The binary for cc is in /ido5.3_compiler/usr/bin/ so do:
-Step 7: Compiling the recomp compiler in <tt>MSYS2 MSYS</tt>
++Step 7: Compiling the recomp compiler in <tt>MSYS2 MSYS</tt>
In MSYS2 MSYS run in the directory mk64/tools/ido5.3_recomp/:
-O2 is an optional optimization flag.
-Step 8: Compile mk64 in <tt>MSYS2 MinGW x64</tt>
++Step 8: Compile mk64 in <tt>MSYS2 MinGW x64</tt>
In /mk64/ run:
Replace # with your number of CPU cores for quicker compilation.