Hi Everyone!

I followed the instructions at the official wiki to get started with allegro.cc (Windows, Code::Blocks and Allegro 5). I chose the dynamic linking, because I usually prefer dynamic linking.
I think I did everything right, and the compiler built the project successfully. However, when I run my application, I get an error (see attached picture). The application is a simple program for testing initialization:

I tried this also, but nothing.

I do not know what I did wrong, but I will try to link statically, and update the post.

Thank you for any advance,
Lasoloz.

Update - here I my specs:
Windows 10 64bit
Code::Blocks 13.12 with MinGW 4.7.1
allegro-5.0.10-mingw-4.7.0

I also downloaded MinGW version 4.8.1, and I made a new compiler profile with new toolchain executables. After this I created a new Project with the new compiler and the new libraries: same error. After copying the libstdc++-6.dll (this question) I get segmentation fault.

I don't know. I have the default MinGW compiler what I have downloaded with Code::Blocks and I also have a compiler on the "C" drive. This is the first time I get this error (I have built a lot of SDL projects) and I have the Code::Block's compiler chosen in properties.
Also, I set up a statically linked version of the program, but I can't compile. When I use the "-static-libstdc++" command it says unrecognized command, when I don't use it wants the "__gxx_personality_v0".
So, if I have problems with compiler setup, what should I do?

(There are some pictures about my configuration for reference)
{"name":"610190","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/b\/7\/b77b01feba2603f384b4d010a9adfd49.png","w":757,"h":575,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/b\/7\/b77b01feba2603f384b4d010a9adfd49"}
{"name":"610191","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/0\/2\/0230c3312a296423081e16d12ac2ac06.png","w":1041,"h":727,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/0\/2\/0230c3312a296423081e16d12ac2ac06"}

EDIT:
I deleted the second MinGW compiler, still nothing.

EDIT2:
I looked up for the dlls with where. Nothing, they are not present in any path variables, however I have old, dumped projects containing it.
The truth is, I don't really know the use of these path variables.

I have g++ set as c++ default compiler. See the second post's image.

You're mixing versions of MinGW. Your binaries from allegro.cc/files are built with a different version of MinGW than comes with CodeBlocks :

I offer Binaries for MinGW 4.8.1 and Allegro 5.1.X at the following two links if you're interested :

https://sourceforge.net/projects/unofficialmingw/

https://sourceforge.net/projects/unofficialallegro5distribution/

I followed this wiki page configuring Allegro. There is a picture, where MinGW libraries are linked after Allegro. The compiler does not throw any errors, so I guess, the linking order is good . The compiler/library mismatch can be an error, I will try to do something with it, as you said.
Currently I'm on linux, but I will update this post after testing.

UPDATE:
I tried with MinGW 4.8.1 from that unofficial build. I get type errors within the io.h.
Next I tried allegro-5.0.10-mingw-4.5.0 library with MinGW 4.5.4 - reference error to al_install_system. So what's next? I think I will get back to SDL, because this Allegro seems to be hard.

(I also updated the question with my specs)

OK. I will try to start everything from scratch. I will tell you if it works, but until Monday I can't test it.

It is still Sunday in Romania.

Either I haven't been paying attention or you never said why you're working with Allegro in Windows. Are you just trying to make a Windows build because it's a popular platform? Or is there some other reason you aren't working with Allegro in Linux? It's generally much easier in Linux.

My advice is rest assured Allegro is Windows compatible and works just fine. Windows is always a nightmare to setup builds though... If you feel yourself getting fed up then put the Windows build on hold and switch to Linux to just get some programming done! Allegro itself is mostly platform independent so you won't have to worry about incompatibility with Windows if you don't use platform specifics yourself. Once you have something that you actually want to release then you can worry about getting a Windows build made (you can also recruit help from the community if necessary).

OK, I tried on Linux. No errors! I used the same program, and it worked. So, should I build my own Allegro version from source on Windows too? It is harder than on Linux? (I mean, here I just used make commands, but on Windows I need to link a lot of libraries to Code::Blocks)

Are you using the -std=c++11 flag anywhere? I read in another thread that was causing problems.

There's a discussion of your problem here :
https://sourceforge.net/p/mingw/bugs/2024/?page=0

I think the key is not to use anything that causes ANSI code checks.

And btw, you don't have to build any of those other libraries, because I've already built all the dependencies for you in my Allegro binary package.

Hi!

Just to say that i had the same problem with Code::Blocks 16.x and Allegro 5.0.10-MinGW 4.7 in a new computer. I have fix it in one minute with the Binaries for MinGW 4.8.1 and Allegro 5.1.X from Edgar Reynaldo. I have to mention that i needed to copy-pasted the dlls from bin directory in SysWOW64 and it works!.

Thanks vey very much Edgar !!.