Thread: [Dev-C++] Fw: [WCS] Problem devcpp / allegro - conflicting headers
Open Source C & C++ IDE for Windows
Brought to you by:
claplace
|
From: jansb000 <jan...@pl...> - 2004-07-15 22:15:52
|
One of the developers on my project on SourceForge is experiencing problems with devcpp in combination with the allegro devpak. It seems that the headerfile wingdi.h is conflicting with allegro.h Any information on this topic? ----- Original Message ----- From: <ka...@po...> To: <wcs...@li...> Sent: Thursday, July 15, 2004 11:11 PM Subject: [WCS] Problem with dev-cpp > Hey > I have a problem with dev-cpp and allegro. Dev-cpp is quite new tool for me and i can't understand one thing. when i'm compiling projects from WCS i have planty errors from allegro headers about BITMAP struct, but when i'm compiling any example programs from allegro everything is ok. > > Beetle > |
|
From: Michal M. <mi...@mo...> - 2004-07-15 22:56:09
|
you have to include winalleg.h if you want to include any windows specific header file, e.g.: #include <allegro.h> #include <winalleg.h> #include <wingdi.h> more detailed description is in the allegro manual in the "Windows specifics" section jansb000 wrote: > One of the developers on my project on SourceForge is experiencing problems > with devcpp in combination with the allegro devpak. It seems that the > headerfile wingdi.h is conflicting with allegro.h > > Any information on this topic? > > ----- Original Message ----- > From: <ka...@po...> > To: <wcs...@li...> > Sent: Thursday, July 15, 2004 11:11 PM > Subject: [WCS] Problem with dev-cpp > > > >>Hey >>I have a problem with dev-cpp and allegro. Dev-cpp is quite new tool for > > me and i can't understand one thing. when i'm compiling projects from WCS i > have planty errors from allegro headers about BITMAP struct, but when i'm > compiling any example programs from allegro everything is ok. > >>Beetle |
|
From: jansb000 <jan...@pl...> - 2004-07-16 20:43:39
|
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. ----- Original Message ----- From: "Michal Molhanec" <mi...@mo...> To: "jansb000" <jan...@pl...> Cc: <dev...@li...>; <ka...@po...> Sent: Friday, July 16, 2004 12:56 AM Subject: Re: [Dev-C++] Fw: [WCS] Problem devcpp / allegro - conflicting headers > you have to include winalleg.h if you want to include any windows > specific header file, e.g.: > > #include <allegro.h> > #include <winalleg.h> > #include <wingdi.h> > > more detailed description is in the allegro manual in the "Windows > specifics" section > > jansb000 wrote: > > > One of the developers on my project on SourceForge is experiencing problems > > with devcpp in combination with the allegro devpak. It seems that the > > headerfile wingdi.h is conflicting with allegro.h > > > > Any information on this topic? > > > > ----- Original Message ----- > > From: <ka...@po...> > > To: <wcs...@li...> > > Sent: Thursday, July 15, 2004 11:11 PM > > Subject: [WCS] Problem with dev-cpp > > > > > > > >>Hey > >>I have a problem with dev-cpp and allegro. Dev-cpp is quite new tool for > > > > me and i can't understand one thing. when i'm compiling projects from WCS i > > have planty errors from allegro headers about BITMAP struct, but when i'm > > compiling any example programs from allegro everything is ok. > > > >>Beetle > > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click > _______________________________________________ > Dev-cpp-users mailing list > Dev...@li... > TO UNSUBSCRIBE: http://www23.brinkster.com/noicys/devcpp/ub.htm > https://lists.sourceforge.net/lists/listinfo/dev-cpp-users > > ================================================================ > Deze e-mail is door E-mail VirusScanner van Planet Internet gecontroleerd op virussen. > Op http://www.planet.nl/evs staat een verwijzing naar de actuele lijst waar op wordt gecontroleerd. |
|
From: Michal M. <mi...@mo...> - 2004-07-16 22:07:50
|
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. |