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.
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?
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.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,090 |
Nodes: | 15 (1 / 14) |
Uptime: | 55:45:23 |
Calls: | 232,714 |
Calls today: | 1 |
Files: | 60,049 |
D/L today: |
14 files (4,772K bytes) |
Messages: | 299,252 |