2023-12-24 19:35 UTC+0100 Enrico Maria Giordano <e.m.giordano@emagsoftware.it>
 * winmake\makefile.bc
 * winmake\makefile.dc
 * winmake\makefile.gc
 * winmake\makefile.pc
 * winmake\makefile.vc
 * winmake\makefile.wc
 * winmake\compile.mak
   ! added new macros CC_CMD_NOWARN and CCC_CMD_NOWARN to silence contrib warnings
 * contrib\gtwvw\gtwvw.c
 * contrib\gtwvg\gtwvg.c
 * contrib\tipssl\inetssl.c
 * contrib\hbssl\ssl.c
 * contrib\hbssl\sslctx.c
   ! fixed compiler warnings
2023-12-24 19:35 UTC+0100 Enrico Maria Giordano <e.m.giordano@emagsoftware.it>
 * contrib\unicode\hbencode.c
   ! fixed compiler warnings
Il 24/12/2023 19:46, Enrico Maria Giordano ha scritto:
2023-12-24 19:35 UTC+0100 Enrico Maria Giordano <e.m.giordano@emagsoftware.it>
* winmake\makefile.bc
* winmake\makefile.dc
* winmake\makefile.gc
* winmake\makefile.pc
* winmake\makefile.vc
* winmake\makefile.wc
* winmake\compile.mak
! added new macros CC_CMD_NOWARN and CCC_CMD_NOWARN to silence
contrib warnings
* contrib\gtwvw\gtwvw.c
* contrib\gtwvg\gtwvg.c
* contrib\tipssl\inetssl.c
* contrib\hbssl\ssl.c
* contrib\hbssl\sslctx.c
! fixed compiler warnings
2023-12-24 19:35 UTC+0100 Enrico Maria Giordano <e.m.giordano@emagsoftware.it>
* contrib\unicode\hbencode.c
! fixed compiler warnings
Now I get no more warnings using MSC32. I have to try MSC64 now...
Now I get no more warnings using MSC32. I have to try MSC64 now...
Cool Enrico thx. Just one observation, it seems when you added:
CC_CMD_NOWARN and CCC_CMD_NOWARN
You did not disable warnings for the other compilers this can be
confusing to future contributors. I beleive iyt sshould be correctly
defined for all compilers where it is defined.
I also noticed that now some project are compiled using boh CC_CMD* and CCC_CMD* that alxo maybe confussing.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 304 |
Nodes: | 16 (3 / 13) |
Uptime: | 34:55:40 |
Calls: | 6,822 |
Calls today: | 2 |
Files: | 12,335 |
Messages: | 5,407,185 |