Some might say that the ps2dev toolchains and tools are a part of the vital data and they would therefor like to have these tools on their backup drive.
Most people install Cygwin into C:\Cygwin and many of these people reinstall Windows frequently and if they are sane they have a different drive for storing all their vital files, like for instance a D drive. Its not always possible to do this because many unix functionalities are built into DLL’s, however it should be possible for the most part. To avoid this use the flag -mno-cygwin when linking your object files to an executable.
You might eventually code some tools which can be used with your projects which build with gcc (not ee-gcc) and once you compiled these, you will realize that if you try to run them outside of cygwin, they will require cygwin1.dll. Cygwin Tipsīuilding Windows Executables Which Do Not Rely On Cygwin1.dll
This will download and build the latest version of PS2SDK for you. Note: Its best to avoid building sources in paths with spaces, for instance /home/joe doe/, before doing the checkout use the command pwd to see if you are in a directory with spaces, if thats the case checkout the files in another directory. Log into Cygwin and get the toolchain script by checking it out from git with the command listed below. The git repository is available at Github. Git is a distributed source control tool which allows many people to work on the same source code. What you need now is the famous toolchain script from Dan Peori (ooPo), it is available from the PS2DEV git repository on GitHub. In case Cygwin complains about other missing programs, just use setup.exe to download and install them.
Note about setup.exe: setup.exe keeps downloaded files from different mirrors in different folders, which means that it will download everything you already have downloaded and installed again if you hange mirrors, so don’t :) For compiling the PS2 toolchain, you need the following packages besides from the preselected packages.ĭownload and install them with setup.exe. Download setup.exe select a mirror and the packages you want to install and it will download and install them for you. Therefor I prefer Cygwin.Ĭygwin has a very easy to use interface for installing, namely setup.exe. But the problem with MinGW is that it is not as mature as Cygwin and therefor problems do (and will) occour. Some claim the Cygwin is bloated and they prefer MinGW, which is a lightweight variant of Cygwin. Not to mention the amount of hack-work you will avoid (eg. If you think about it for a minute, you will realize that if you want to be part of a community and contribute it would be quite pointless to use a different enviroment than everyone else. This is the beauty of Cygwin, you get the same development enviroment as every one else. You need Cygwin in order to compile the PS2 ports of GCC ( GNU C Compiler) aswell as other PS2 projects.Īnother reason to get Cygwin is if you create a project which compiles under Cygwin using makefiles and other unix tools, its very likely that this project will also compile on other systems such as Linux, MacOS, etc. Cygwin is a collection of unix tools ported to Windows, which enables you to do tasks which would normally only be possible in a unix enviroment. Getting Cygwinįirst of all you need to install Cygwin. As alternative you can try to build them in MinGW by following this tutorial.
The PS2 toolchains do currently not build in Cygwin (see this thread ). Building PS2 Toolchains and PS2SDK in Cygwin