The 05 november 2006 build is out.

[gjsmo]

Got an error message saying an entry point in wxmsw26u_gcc_cb.dll is missing.
I'm attaching the popup for reference.

Try downloading the DLL again. Unzip it into your WINDOWS folder - you won't have to do it again unless you still get the error. If you have C:\MinGW\bin (or its equivalent) in your PATH, unzip it there instead. You really don't want to clutter up your WINDOWS folder if you can help it. Delete one in your codeblocks folder - it's probably corrupt (no, it is corrupt).

[Walter Z]

Simple applications that make use of multithreading shouldn't need any additional compiler flags.

Thanks!

[Belgabor]

Got an error message saying an entry point in wxmsw26u_gcc_cb.dll is missing.
I'm attaching the popup for reference.

Try downloading the DLL again. Unzip it into your WINDOWS folder - you won't have to do it again unless you still get the error. If you have C:\MinGW\bin (or its equivalent) in your PATH, unzip it there instead. You really don't want to clutter up your WINDOWS folder if you can help it. Delete one in your codeblocks folder - it's probably corrupt (no, it is corrupt).

I would recommend against that. Put it in the same folder as the C::B executable.

[Freddy]

I include <windows.h> but, code completion for some API's like CreateFile() doesn't work. Although for API's like MessageBox() is does work.
Any ideas?

[TDragon]

I include <windows.h> but, code completion for some API's like CreateFile() doesn't work. Although for API's like MessageBox() is does work.
Any ideas?

Win32 uses macros. Lots of them. In strange and wonderful/awful ways. Code completion doesn't like macros.

The most common culprit is the fact that a ton of Win32 functions are actually macros typedef-ed to either the ANSI or Unicode version of the actual function. Whether this is the limiting factor in your case, I couldn't say. Suffice it to be known that, as always, code completion is a work in progress with known bugs and limitations.