The quickest and easiest way to set up your environment on Windows

[gibbocool]

So you want to compile your C/C++ code to work on the PSP and want a quick and easy method to do so?
You've come to the right place! Here I present two options: DevkitPro and MinPSP.

Cygwin is basically a linux-like environment for windows. MinGW is another example of this.
The traditional way to develop on the PSP with windows is to install cygwin, and use it to compile the psp tool chain, which allows you to compile your PSP apps. What DevkitPro and MinPSP does is misses out the middle step - it is a precompiled development environment.

DevkitPro comes with MinGW. The best thing about DevkitPro is that it uses an installer and updater that downloads the latest toolchain, and installs everything for you.

Note that these precompiled envoronments aren't a complete substitute for cygwin, but they gets you started nice and quick. Advanced users may want to get cygwin running.

So what is the difference between DevkitPro and MinPSP? DevkitPro uses MinGW, whereas MinPSP lets you use your windows command prompt.

*Update*

It seems that DevkitPro hasn't been updated in a while, so I recommend MinPSP.

MinPSP

Download DevkitPro
DevkitPro Official Site

[Insert_Witty_Name]

I never tried one of these pre-compiled packages, but I've heard it's hard (or not possible)  to install 3rd part libraries (libpng, libmad) etc on them.

Is that true?

[@rt]

Do you have to do anything different with your makefile?
My programs compile in cygwin, but in devkitpro I use the same code and ge tthis

Code:

make: psp-config: Command not found
Makefile:25: /lib/build.mak: No such file or directory
make: *** No rule to make target '/lib/build.mak'. Stop.

[gibbocool]

@ IWN: I installed zlib and libpng flawlessly, but when i try and compile a program requiring libpng, i get

Code:

graphics.o: In function `imageSave':
graphics.c:(.text+0xee0): undefined reference to `png_create_write_struct'
graphics.c:(.text+0xef0): undefined reference to `png_create_info_struct'
graphics.c:(.text+0xf04): undefined reference to `png_init_io'
graphics.c:(.text+0xf30): undefined reference to `png_set_IHDR'
graphics.c:(.text+0xf3c): undefined reference to `png_write_info'
graphics.c:(.text+0xfcc): undefined reference to `png_write_row'
graphics.c:(.text+0xff0): undefined reference to `png_write_end'
graphics.c:(.text+0xffc): undefined reference to `png_destroy_write_struct'
graphics.c:(.text+0x1044): undefined reference to `png_set_IHDR'
graphics.c:(.text+0x1050): undefined reference to `png_write_info'
graphics.c:(.text+0x1068): undefined reference to `png_destroy_write_struct'
graphics.o: In function `imageLoad':
graphics.c:(.text+0x28b8): undefined reference to `png_create_read_struct'
graphics.c:(.text+0x28dc): undefined reference to `png_set_error_fn'
graphics.c:(.text+0x28e4): undefined reference to `png_create_info_struct'
graphics.c:(.text+0x28f8): undefined reference to `png_init_io'
graphics.c:(.text+0x2904): undefined reference to `png_set_sig_bytes'
graphics.c:(.text+0x2910): undefined reference to `png_read_info'
graphics.c:(.text+0x2938): undefined reference to `png_get_IHDR'
graphics.c:(.text+0x2974): undefined reference to `png_destroy_read_struct'
graphics.c:(.text+0x2a2c): undefined reference to `png_set_strip_16'
graphics.c:(.text+0x2a34): undefined reference to `png_set_packing'
graphics.c:(.text+0x2a68): undefined reference to `png_get_valid'
graphics.c:(.text+0x2a80): undefined reference to `png_set_filler'
graphics.c:(.text+0x2ad4): undefined reference to `png_read_row'
graphics.c:(.text+0x2b48): undefined reference to `png_read_end'
graphics.c:(.text+0x2b58): undefined reference to `png_destroy_read_struct'
graphics.c:(.text+0x2b9c): undefined reference to `png_set_tRNS_to_alpha'
graphics.c:(.text+0x2bac): undefined reference to `png_set_palette_to_rgb'
graphics.c:(.text+0x2bdc): undefined reference to `png_destroy_read_struct'
graphics.c:(.text+0x2c04): undefined reference to `png_set_gray_1_2_4_to_8'
graphics.c:(.text+0x2c34): undefined reference to `png_destroy_read_struct

@ Art: looks like you need to add the directory to your Path correctly -
Go to System Properties > Advanced > Environment Variables > Edit the Path system variable and add c:\devkitPro\devkitPSP\bin. Make sure it is seperated by a semicolon.

[Insert_Witty_Name]

... @ IWN: I installed zlib and libpng flawlessly...

Doesn't look too flawless

This is why I stay away from pre-built binaries.

[jsharrad]

Are you linking zlib and libpng when you compile that?  looks like it hasn't been linked from those errors

[jono]

Have you added -lpng -lz ect. to the libs line in your makefile?
[EDIT] Oops, didn't realise thats what jsharrad said.

If it is actually a problem with where the libraries are located you could just find one of those dev library installers that were around, they just extract all the files to the correct directory and off you go.

I use this devkitpro in my breaks at uni because I can install the compiler and libraries on a computer in about two minutes. I've just got the devkitpro installer and the devlibrary installer on the root of my memory stick aswell as crimson editor just in case theres no source editor.

I have cygwin setup on my home computer however. And I also prefer it, I'm in the process of migrating to linux so it's been helpful to already understand some of the command line functions.

[ancoldsun]

So which one is better ? cygwin or devkitpro ?

[gibbocool]

Cygwin is better as it's a more complete environment.

@jsharrad yes i have linked with those. I'm actually trying to compile flatmush's text editor. I actually tried the binary libraries before i tried compiling my own - same errors both times.

[Flatmush]

If you only want to compile my editor, then I could remake it to use tga's instead of png's and save you the bother, but that wouldn't help your library problem.

[gibbocool]

If you only want to compile my editor, then I could remake it to use tga's instead of png's and save you the bother, but that wouldn't help your library problem.

If i really wanted to, I would have done it myself
I'm sure it's just a once-off thing. Could someone else give it a go?
I wont be making programs using png's any time soon it seems

[KeegY]

mmm, i first started with one of the "pre-compiled" ones and at the time i know nothing different. i also found it hard to update the toolchain etc, so i ended up just placing the headers and stuff in the directory with my main.c. it worked until it all got a bit over my head, and IWN helped me get on track with cygwin and now things are fine, so my advide is that if you can, use cygwin, less hassle.

[Insert_Witty_Name]

Indeed.

These pre-compiled things are fine....

Until you need to update the SDK, or use a third-party library (which you will need after before you know it).

[neo]

...or just run an *nix OS environment?

[yaustar]

Updating the toolchain is pretty simple with DevkitPro as it works like cygwin. Load the original exe and click update. The only downside is that it only gets updated as often as DevkitPro and not the toolchain. Libraries should be the same as cygwin as it uses minsys (a bash shell). The only difference is that you need to use an external SVN client to download the source.