I don't know what guide you're following, but if it is this one:

http://wiki.allegro.cc/index.php?title=Windows_Vista,_Code::Blocks_10.05_and_Allegro_5

"it" is Project->Build Options->Compiler Settings->#defines. Just type ALLEGRO_STATICLINK there.
Or you could also just type:

#define ALLEGRO_STATICLINK

in the very beginning of your code and it should work fine.

If you managed to follow the tutorial to this point, it should be working now. If it isn't, please post any errors you got when trying to compile a project. There's a nice example for testing in here: http://wiki.allegro.cc/index.php?title=Allegro_5_Tutorial/Displays
Just copy the first block of code.

Did you added C:/MinGW/bin(or whenever your bin folder is in your installation) to your PATH environment variable? Check also if MINGDIR is there.

Finally, check if Code::Blocks is using the correct MinGW installation. Go to Settings->Compiler and debugger settings->Toolchain Executables and see if the compiler's installation directory is the correct path to your MinGW installation(Sometimes the path is to the built-in MinGW from C::B, although this shouldn't pose these exact same problems. Just change it to your custom installation)

EDIT: After you are done, press Ctrl+F11 to rebuild your project from scratch.

When you say that path and MINGDIR are on the same folder, do you mean the exact same folder?

path should be C:/MinGW/bin
MINGDIR should be C:/MinGW

I know I'm insisting in something apparently too small, but your problem is definitely in your MinGW installation. You don't need to uninstall Allegro or C::B, but you may try re-checking the compiler.
Those two shared libraries you are getting errors from are MinGW's. If they are giving errors, either your MinGW installation has a problem, or you're missing something when you're linking you project.

Since I saw you changed your installation already, you might as well check if you haven't missed any of these libraries in your linker(but only if you're linking statically):

1 - libgdiplus.a
2 - libuuid.a
3 - libkernel32.a
4 - libwinmm.a
5 - libpsapi.a
6 - libopengl32.a
7 - libglu32.a
8 - libuser32.a
9 - libcomdlg32.a
10 - libgdi32.a
11 - libshell32.a
12 - libole32.a
13 - libadvapi32.a
14 - libws2_32.a
15 - libshlwapi.a

If none of this helps, I'm over my capacity here(I'm really just a beginner witch spent a lot of time installing this on a few PCs). I'll continue helping whenever I can, though.

Hello,

I have recently decided to try loading code blocks with allegro 5.0.0 and followed the directions from http://www.allegro.cc/forums/thread/606041. Everything seemed to be working just fine but when I attempted step 17 I noticed that the file "liballegro.dll.a" was actually in another path. I don't know if that is what has been causing the errors during the build stage. The path that I found this file in is C:\CodeBlocks\MinGW\allegro\build\lib. anyhow, it does not seem to build correctly as I have received a whole slew of errors:

C:\Documents and Settings\Harold.SAMURAI\Desktop\Haledemus\main.cpp|2|error: allegro5/allegro.h: No such file or directory|
C:\Documents and Settings\Harold.SAMURAI\Desktop\Haledemus\main.cpp||In function 'int main(int, char**)':|
C:\Documents and Settings\Harold.SAMURAI\Desktop\Haledemus\main.cpp|7|error: 'ALLEGRO_DISPLAY' was not declared in this scope|
C:\Documents and Settings\Harold.SAMURAI\Desktop\Haledemus\main.cpp|7|error: 'display' was not declared in this scope|
C:\Documents and Settings\Harold.SAMURAI\Desktop\Haledemus\main.cpp|9|error: 'al_init' was not declared in this scope|
C:\Documents and Settings\Harold.SAMURAI\Desktop\Haledemus\main.cpp|14|error: 'al_create_display' was not declared in this scope|
C:\Documents and Settings\Harold.SAMURAI\Desktop\Haledemus\main.cpp|20|error: 'al_map_rgb' was not declared in this scope|
C:\Documents and Settings\Harold.SAMURAI\Desktop\Haledemus\main.cpp|20|error: 'al_clear_to_color' was not declared in this scope|
C:\Documents and Settings\Harold.SAMURAI\Desktop\Haledemus\main.cpp|22|error: 'al_flip_display' was not declared in this scope|
C:\Documents and Settings\Harold.SAMURAI\Desktop\Haledemus\main.cpp|24|error: 'al_rest' was not declared in this scope|
C:\Documents and Settings\Harold.SAMURAI\Desktop\Haledemus\main.cpp|26|error: 'al_destroy_display' was not declared in this scope|
||=== Build finished: 10 errors, 0 warnings ===|

Please help me as this is my second attempt at this and it has been an utter failure

Thanks anyway. I will try again when I get a chance and if I ever get it to work I will post something up to help the next guy who goes down the same path as me.

Hi guys,

sorry, I did not know where to post this question but I finally was able to laod codeblocks and allegro into my system and it works. Then I looked at the allegro site and found this:

Allegro 5 is the latest major revision of the library, designed to take advantage of modern hardware (e.g. hardware acceleration using 3D cards) and operating systems. Although it is not backwards compatible with earlier versions, it still occupies the same niche and retains a familiar style.

My book is for allegro 4.2! does this mean I cannot use allegro 5.0? Just checking because I have rammed my head up against a brick wall year after year after year trying to match up compilers and books to no avail. Now that I thought I have everything set I find that I may be mistaken. Please tell me I can us 5.0 because I am about to lose my mind!!!

You can still use CodeBlocks (with MinGW GNU compiler) and Allegro 4. Once you learn enough about programming and are more familiar with Allegro you can then make the move to Allegro 5. 4 is a very good spot to start from, it's easy to use.

I'm using both myself. I'm currently updating an older game of mine created with the classic Allegro and currently using the latest version of Allegro 4. And I am creating newer versions of other games with Allegro 5.

If you have a book on game programming, by all means keep using Allegro 4, game programming concepts are independent of libraries so you'll still probably pick up some valuable information from the book. They obviously have good taste in libraries.