1. Install Cygwin on your PC (
http://www.cygwin.com/)
2. Install Zerohour's PC-based GCC Amiga cross-compiler. (
http://http://www.zerohero.se/cross/os3.html)
3. Install WinUAE on your PC. Share a directory on your PC between WinUAE and your "real Amiga" using Samba and your PCMCIA Ethernet card
4. Create your C/C++ sources using one of the many freely available code editors on the PC. (I use NotePad++
http://notepad-plus.sourceforge.net/uk/site.htm, but the choice is wide and varied)
5. Save your sources from the editor to the shared WinUAE folder.
6. Compile those sources with lightening fast speed using your Cygwin based Bash interface and the cross-compiler you installed in step #2. You might have to learn some "Makefile" basics, beforehand and create yourself a project Makefile. (depends how complex your project is, simple compiles will not need a Makefile)
7. Test the binary the cross-compiler outputs with your WinUAE set-up (installed in step #3). If the code crashes WinUAE...no problem! You can reset WinUAE and be back in action within a matter of seconds.
8. Once you are happy with the binary tests you have done in WinUAE, switch over to your "Real" Amiga and execute the exact same binary from the shared PC Samba directory for the “final test”.
This is the best _modern_ pipeline when it comes to compiling Amiga apps. Sure, you can setup a native Amiga environment, but you will find it clumsy and slow, particularly on an unexpanded a1200 compiling C++ sources. Crashes will also drive you around the bend when developing on a native Amiga, whereas GURUs in an instance of WinUAE running on a PC are a mere "irritant"