Good that you got my reasons.
Here I am using a Windows machine.
Originally Posted by .Hz
My Sony Vaio i3 Notebook is Windows 7 64 bits Basic powered, where I use Crimsom Editor to edit GSM source code.
For the compiling job I use the the Yoshi314's ps2toolchain VM (Virtual Machine) inside Oracle VirtualBox. It was originally made just for OPL (Open PS2 Loader) but after some GSM source code changing I was able to be compiled it there too ;-)
Inside this "VM" (Virtual Machine), I can access a real, small, dedicated FAT32 partition located into my notebook where all source files are hosted, and an simple Linux script is responsible for all copying/compiling/copying tasks between VM and real HDD.
So every time I got a resulting GSM.ELF file (ELF = Executable Link File), it's time to start the PCSX2 0.9.7 3113 (PS2 emulator) and test the results.
I know that all this stuff can be considered a rigmarole and my "emulated" isn't an appropriate environment for final testing... But what I can do? I'm doing my best here, that is what I can use for now.
When I consider all the stuff be functional (respecting all the emulator restrictions), it will time to test into a real PS2 Console (via pendrive and/or PS2 Link).
Finally, I will invite dlanor to make some peer reviewing on source code (when he want and if he want... There is no obligation on doing this... Respect among PSX-Sceners is a must-have attitude)... And when all this stuff be considered ready, a new release will be published. And we'll be very happy when this happens.
Is it pretty simple, isn't it? :-D
Now I'll try finish to read an IDC MIPS doc chapter and do more coding stuff before closing my eyes... zzzzzzzzzzzzzzzzzzz
doctorxyz's PS2 & PS3 stuff: (http://psx-scene.com/forums/f257/doctorxyzs-ps2-ps3-stuff-101348/)