On Sat, Dec 06, 2025 at 09:05:21AM -0800, Ben Collver wrote: > On Sat, Dec 06, 2025 at 12:43:13PM +0000, > [email protected] wrote: > > I use BCC for some things, so I'd like to try this. But I may not have time > > to look at it until a week from now. (*If anyone else wants to do it, don't > > wait on me, go ahead.*) > > I'll give it a shot and let you know how it goes.
I am working on this. Here is a status update: The BCC in FreeDOS 1.3 and 1.4 is 16-bit hosted. I configured OpenWatcom to target a 16-bit host. I fetched the dev86 bcc version 0.16.21 source code from: <https://github.com/lkundrak/dev86> The sources have long file names, so i enabled DOSLFN. I configure DJGPP to get GNU make and gperf, as required by dev86. I learned to avoid OWCC.EXE and use WCL.EXE instead. [1] I built the compiler toolchain. Then i tried to build libc. I became frustrated with the libc Makefiles. Now i plan to "flatten" the build into a batch file instead of using GNU make. I plan to check back in after a few days. -Ben [1] See cguide.pdf, 16-bit Topics, 6.9 Memory Layout, p.122 (pdf.134) > In addition to these special segments, the following conventions > are used by Open Watcom C/C++. > > 1. The "CODE" class contains the executable code for your > application. In a small code model, this consists of the segment > "_TEXT". In a big code model, this consists of the segments > "<module>_TEXT" where <module> is the file name of the source file. This is true when using wcl.exe. However, owcc.exe ignores -mcmodel=large and crams all of the code into one big _TEXT segment instead of using multiple smaller <module>_TEXT segments. _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
