Re: [Dev-C++] Fw: [WCS] Problem devcpp / allegro - conflicting headers

[Michal M. <mi...@mo...>]

You have two options:
a) define __GTHREAD_HIDE_WIN32API symbol (e.g. Project\Project 
Options\Parameters and write -D__GTHREAD_HIDE_WIN32API in C++ compiler)
b) upgrade to newer MinGW where is this problem fixed

You know, sometimes is useful to read Allegro documentation, especially 
FAQ section.

jansb000 wrote:
> We want to do exactly the opposite. We want to write code that compiles
> out-of-the-box with DEVCPP and DJGPP. We only want to use allegro functions
> and not something from Win32 specific. After all that was the reason for our
> project to choose a multi-platform library like allegro.
> 
> It appears that when we include <iostream> we automatically get a number of
> Windows specifc headers (like wingdi.h). Unfortunately allegro and wingdi
> both use a BITMAP structure so we cant compile our sourcecode as long as it
> includes <iostream>.
> 
> When we use the DEVPAK for Allegro 4.1.14, what type of project do we have
> to choose to get an allegro-only project. I remember that in the past with
> DEVCPP 4.02 and an old Allegro DEVPAK I had to select a console application,
> but with the new versions of DEVCPP and allegro that options doesn't exsist
> anymore.