1. Forum
  2. FidoNet
  3. TUB

  • slib/hntypes.h slib/typedefs.h

    From Serguei Trouchelle@2:550/4077.101 to All on Sunday, November 16, 2003 21:36:24
    These files' contents cause compiling problems under WinNT environment.

    Some `typedefs' double %watcom%\h\nt\windef.h, and it causes fatal error when using Win32API. I think these problems will be with OS/2 API too.

    I think, all current definitions have to be transferred to #ifdef __UNIX__ or #ifdef __GNUC__ blocks, leaving original Scott's definitions in #ifdef __WATCOM__ or something.

    Serguei Trouchelle
    --- timEd/386 1.10.y2k+
    * Origin: Send more complaints! (2:550/4077.101)
  • From Bo Simonsen@2:236/100 to Serguei Trouchelle on Tuesday, November 18, 2003 16:34:44
    Hello Serguei!

    Nov 16 21:36 03, Serguei Trouchelle wrote to All:

    These files' contents cause compiling problems under WinNT
    environment.

    Some `typedefs' double %watcom%\h\nt\windef.h, and it causes fatal
    error when using Win32API. I think these problems will be with OS/2
    API too.

    Aha,

    I think, all current definitions have to be transferred to #ifdef __UNIX__ or #ifdef __GNUC__ blocks, leaving original Scott's
    definitions in #ifdef __WATCOM__ or something.

    Why?

    Regards,
    Bo

    --- Msged/LNX 6.1.2 (Linux/2.4.18-586tsc (i586))
    * Origin: The Night Express, Roennede Dk (2:236/100)
  • From Serguei Trouchelle@2:550/357.1 to Bo Simonsen on Tuesday, November 18, 2003 20:39:00
    These files' contents cause compiling problems under WinNT
    environment.

    Some `typedefs' double %watcom%\h\nt\windef.h, and it causes fatal
    error when using Win32API. I think these problems will be with OS/2
    API too.

    Aha,

    I think, all current definitions have to be transferred to #ifdef __UNIX__ or #ifdef __GNUC__ blocks, leaving original Scott's
    definitions in #ifdef __WATCOM__ or something.

    Why?

    Because Watcom WinAPI (and OS/2 Toolkit too) already has most of it.

    By the way, can Cygwin reproduce your environments? I want to check code for gcc-compliance when making changes.

    Serguei Trouchelle
    --- timEd/386 1.10.y2k+
    * Origin: Was sollen wir trinken Sieben Tage lang... (2:550/357.1)
  • From Bo Simonsen@2:236/100 to Serguei Trouchelle on Friday, November 21, 2003 00:51:38
    Hello Serguei!

    Nov 18 20:39 03, Serguei Trouchelle wrote to Bo Simonsen:

    I think, all current definitions have to be transferred to #ifdef
    __UNIX__ or #ifdef __GNUC__ blocks, leaving original Scott's
    definitions in #ifdef __WATCOM__ or something.

    Why?

    Because Watcom WinAPI (and OS/2 Toolkit too) already has most of it.

    By the way, can Cygwin reproduce your environments? I want to check
    code for gcc-compliance when making changes.

    I really think so :-) But I haven't tried!

    Regards,
    Bo

    --- Msged/LNX 6.1.2 (Linux/2.4.18-586tsc (i586))
    * Origin: The Night Express, Roennede Dk (2:236/100)