1)Scroll down to the Binary section and download the Windows development library

Every extension libary has 3 essential parts:

1. The header file.
2. The lib file.
3. The *.dll file(s)

They're all set up pretty much the same way no matter which extension you're setting up.

Open up the zip archive and there should be a folder inside.
Open the folder and it'll contain 2 subfolders.

2)First, open the include subfolder in the archive and extract the header file inside to the SDL subfolder inside of the MinGW include folder. It should be at C:\MinGW\include\SDL.

3)Now find the lib folder from the archive. Take the library file(s) from the archive and put them with the rest of the SDL library files. The MinGW lib folder should be at C:\MinGW\lib.

For certain versions of SDL_image, there will be a x86 folder and a x64 folder inside of the lib folder from the archive. The x86 folder contains the 32bit *.lib files and the x64 bit folder contains the 64bit versions of the library files. If you're compiling a 32bit program, copy the library file(s) from the x86 folder and if you're compiling a 64bit version copy the library file(s) from the x64 folder. By default most compilers compile in 32bit so if you're not sure how you're compiling, try the 32bit libraries first. What matters here is not whether you have 32/64bit windows, but what type of program you're compiling.

If you don't see a x86 or x64 folder inside of the lib directory from the archive, just copy the library file(s) from the lib folder from the archive.

4)Now extract all of the *.dll file(s) from the archive and put them in the same directory as your exe.

Like before, you can copy them to C:\WINDOWS\SYSTEM32 (or C:\Windows\SysWOW64 on 64bit Windows) so your SDL app will find the *.dll(s) even if they're not in the same directory. The problem with this method is if you have multiple SDL apps that use different versions of SDL, you'll have version conflicts. If you have an old version in SYSTEM32 when the app uses the new version you're going to run into problems. Generally you want to have your the *.dll(s) in the same directory as your executable developing and you'll always want to have *.dll(s) in the same directory as the exe when distributing your app.

5)Now in the command line you enter

g++ -o myprogram.exe mysource.cpp -lmingw32 -lSDLmain -lSDL -lSDL_image

to compile your program.

If you were linking SDL_ttf you'd append

-lSDL_ttf

if you were linking SDL_mixer you'd add on

-lSDL_mixer

etc, etc.

6)To use SDL_image make sure to include the header file.

If you were setting up SDL_ttf you'd put

#include "SDL/SDL_ttf.h"

If you were setting up SDL_mixer you'd put

#include "SDL/SDL_mixer.h"

etc, etc.

Now the extension library is all set up.

Now you can use SDL_image functions.

The main one you want to know about is IMG_Load().

Here is a revised version of the image loading function from the previous tutorial. As you can see IMG_Load() functions exactly the same as SDL_LoadBMP(), but there's one big exception: IMG_Load() can load BMP, PNM, XPM, LBM, PCX, GIF, JPEG, TGA and PNG files.

From this tutorial on, PNG image files will be the primary image format used. PNGs have excellent lossless compression.