Re: w32api header problems

2002-01-09 Thread egor duda
Hi! Wednesday, 09 January, 2002 Jean le Roux [EMAIL PROTECTED] wrote: JlR> On Wed, Jan 09, 2002 at 04:47:18PM +0300, egor duda wrote: >> JlR> I've done this but seems to leave my code in a tangle :) >> JlR> I suddenly have parse errors in my own header files, on normal >> JlR> function declerat

Re: w32api header problems

2002-01-09 Thread Jean le Roux
On Wed, Jan 09, 2002 at 04:47:18PM +0300, egor duda wrote: ... > JlR> I've done this but seems to leave my code in a tangle :) > JlR> I suddenly have parse errors in my own header files, on normal > JlR> function declerations. I can only deduce that windows.h is leaving an > JlR> open ifdef or

Re: w32api header problems

2002-01-09 Thread egor duda
Hi! Wednesday, 09 January, 2002 Jean le Roux [EMAIL PROTECTED] wrote: JlR> On Wed, Jan 09, 2002 at 01:07:47PM +0300, egor duda wrote: >> Hi! >> >> Wednesday, 09 January, 2002 Jean le Roux [EMAIL PROTECTED] wrote: >> >> JlR> I need to include /usr/include/w32api/winbase.h in order to use the >>

RE: w32api header problems

2002-01-09 Thread Norman Vine
Jean le Roux writes: >... >//this is where i include the header that make life hard :) > >#ifdef HAVE_WINDOWS_H >#include >#endif > >... > >//this is where the errors occur. >/*other*/ #ifndef max // or #ifndef _WIN32 >int max(const int value_a, const int value_b); //line 283 >int min(c

Re: w32api header problems

2002-01-09 Thread Jean le Roux
Hi > To fix the min and max, define the following before including windows.h: > #define NOMINMAX added that... waiting for compile to complete (Working on a VM... takes forever :) and tada! It's happy and so am I! It still warns me about undefined symbols: make all-recursive make[1]: E

RE: w32api header problems

2002-01-09 Thread Bernard Dautrevaux
> -Original Message- > From: Jean le Roux [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 09, 2002 1:38 PM > To: [EMAIL PROTECTED] > Subject: Re: w32api header problems > > > > int max(const int value_a, const int value_b); //line 283 >

Re: w32api header problems

2002-01-09 Thread Pavel Tsekov
Jean le Roux wrote: > On Wed, Jan 09, 2002 at 12:40:02PM +0100, Pavel Tsekov wrote: > >>Jean le Roux wrote: >> >> >>>On Wed, Jan 09, 2002 at 01:07:47PM +0300, egor duda wrote: >>> >>> Hi! Wednesday, 09 January, 2002 Jean le Roux [EMAIL PROTECTED] wrote: JlR> I need to inc

Re: w32api header problems

2002-01-09 Thread Jean le Roux
> intmax(const int value_a, const int value_b); //line 283 > intmin(const int value_a, const int value_b); //line 284 > string itoa(const int value, const short fix=0); //line 285 ... > common.h:284: parse error before `const' > common.h:285: parse error before `const' Woops.. those lin

Re: w32api header problems

2002-01-09 Thread Jean le Roux
On Wed, Jan 09, 2002 at 12:40:02PM +0100, Pavel Tsekov wrote: > Jean le Roux wrote: > > > On Wed, Jan 09, 2002 at 01:07:47PM +0300, egor duda wrote: > > > >>Hi! > >> > >>Wednesday, 09 January, 2002 Jean le Roux [EMAIL PROTECTED] wrote: > >> > >>JlR> I need to include /usr/include/w32api/winbase.

Re: w32api header problems

2002-01-09 Thread Pavel Tsekov
Jean le Roux wrote: > On Wed, Jan 09, 2002 at 01:07:47PM +0300, egor duda wrote: > >>Hi! >> >>Wednesday, 09 January, 2002 Jean le Roux [EMAIL PROTECTED] wrote: >> >>JlR> I need to include /usr/include/w32api/winbase.h in order to use the >>JlR> GetVolumeInformation(...) system call under windows

Re: w32api header problems

2002-01-09 Thread Jean le Roux
On Wed, Jan 09, 2002 at 01:07:47PM +0300, egor duda wrote: > Hi! > > Wednesday, 09 January, 2002 Jean le Roux [EMAIL PROTECTED] wrote: > > JlR> I need to include /usr/include/w32api/winbase.h in order to use the > JlR> GetVolumeInformation(...) system call under windows. > > JlR> However, as i

Re: w32api header problems

2002-01-09 Thread egor duda
Hi! Wednesday, 09 January, 2002 Jean le Roux [EMAIL PROTECTED] wrote: JlR> I need to include /usr/include/w32api/winbase.h in order to use the JlR> GetVolumeInformation(...) system call under windows. JlR> However, as i metioned in an earlier mail, DWORD seems to not be JlR> defined. I tracked