Read-only archive of the Armageddon Games Forums Archive (2000–2026) · About this archive

Compiling errors of doom, destruction, and doom.

31 replies · 13,289 views · Started 01 December 2016

Here's that guide for using MSYS:

http://pastebin.com/Ygxqe0av

Building ZC With MSYS
[spoiler]
[FONT=Courier New]Building ZC With MSYS
A simple guide by ZoriaRPG.
4th December, 2016

1. If you have not already done so, install MinGW and MYSY on your system.
1a. Be sure to install all the basic packages.
2. Download the ZC '2.50.x' branch to your local filesystem.
3. Download this revised makefile, and keep it handy in the event of errors:
timelord.insomnia247.nl/zc/zc_dev/makefile
4. On your local filesystem, locate and open this path:
drive:\MinGW\lib\gcc\mingw32\5.3.0\include
5. On your local filesystem, open the path to the zc sources, to this point:
drive:\pathto\zeldaclassic-2.50.x\allegro
6. In this 'allegro' directory, you will find:
allegro\
fixed\
allegro.h
winalleg.h
7. COPY (do not move) the two directories, and the two headers, to the path from (4).
8. In the zc files path, make the following directory:
obj\
This should be at the same level as src\, allegro\, bin\, include\, libs\, other\, projects\, and utils\
9. Inside the newly made obj\ directory, create the subdirectory:
parser\
Thus, you should have: drive:\zcfiles\obj\parser
10. On your filesystem, find and open this path:
drive:\MinGW\msys\
11. Run the batch file, msys.bat
12. A terminal window will open.
13. use the 'cd' command to move to the path containing the zc sources and makefile.
NOTE: MSYS uses Linux style paths, not MS-DOS style paths, so the path will be represented as:
DRIVE:/pathto/zeldaclassic-2.50.x/
14. Once the path containing the makefile is your current directory, type the command:
make
15. This will start the building process.
14. if you encounter early errors on missing headers, replace the makefile with the makefile that your downloaded in (3).
15. If you encounter late-compiling header errors, ensure that you copied all the files in steps ( 4 ) to ( 7 ).[/FONT]
[/spoiler]

P.S. I tried merging Gleeok's new drawing stuff, but msys/gcc continuously gave me a nonspecific error generating ffscript.o. I'll re-try, tomorrow, one new entry at a time.

Alright, I went ahead and abandoned the master branch since I don't think I had anything that important in there (..I'll look at it later, anyway). It would be nice to keep the build_modules stuff though, if you don't mind merging the seemingly nothing namespace fixes, etc. over when it happens.