You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
wincon got support for "not-anymore Borland" BC++ 7.0+ (owned by Embercado, CLANG based, supports win32 and win64 [using the "community edition", possibly untested for PDCurses]). It cannot use Borland C 5.5 anymore.
wingui has the old one (supporting Win16 [likely not relevant] and Win32 [not sure if/when this was tested the last time]).
I suggest to add an optional "borland" define to switch back to the old compiler, otherwise use the new one (both compilers for both variants). In any case the 64bit option from the newer compilers should be added, too...
@Bill-Gray Do you have any thoughts about this? Do you have access to bcc32 (5.x) bcc32/bcc64 (newer) bcc32c (is there a bcc64c)?
The text was updated successfully, but these errors were encountered:
@GitMensch the only Borland compiler I have is 5.5.1, running in Wine under Linux. Haven't tried it for a while. I just did, and couldn't get wincon, wingui, or dos flavors to compile. Looking more carefully, I see that BC 5.5 is Win32-only, so the lack of DOS is completely understandable.
Wincon and WinGUI failed due to lack of support for 64-bit integers and lack of stdint.h. I got around those by using -DCHTYPE_32 (i.e, 32-bit chtypes instead of the default 64-bit) and with a few lines to curses.h to cover the "no stdint.h" case. Still various objections from the compiler, and... one could probably work around them, but it sounds as if BC++ 7.0 makes it not really worth the effort.
Seems to me that you might as well go with Borland makefiles that work only with 7.0, and which support 32- and 64-bit compiles. I doubt there will be objections.
Wincon and WinGUI failed due to lack of support for 64-bit integers and lack of stdint.h.
win32 is an old port, when did it stop to work with BCC 5.5 (we may reference an old version to use when removing the support completely)? I personally don't care about BCC in general, mainly about a "clean" PDCurses version including its build system. I think I have a newer Borland compiler on some box and may retry using these (possibly bcc32 bcc64 bcc32c), then making some adjustments to the Makefiles.
wincon got support for "not-anymore Borland" BC++ 7.0+ (owned by Embercado, CLANG based, supports win32 and win64 [using the "community edition", possibly untested for PDCurses]). It cannot use Borland C 5.5 anymore.
wingui has the old one (supporting Win16 [likely not relevant] and Win32 [not sure if/when this was tested the last time]).
I suggest to add an optional "borland" define to switch back to the old compiler, otherwise use the new one (both compilers for both variants). In any case the 64bit option from the newer compilers should be added, too...
@Bill-Gray Do you have any thoughts about this? Do you have access to bcc32 (5.x) bcc32/bcc64 (newer) bcc32c (is there a bcc64c)?
The text was updated successfully, but these errors were encountered: