I tried to make Edlin portable enough so that multiple toolchains would work on it. I normally use Cygwin with GCC and make to compile it, but FreeDOS is a DOS, so I tried to make it so that multiple compilers could compile it. Forgive my wording here...
Anyway, tweaking config.h should take care of the differences in compilers. That file can also be generated through the configure script (as well as the makefile), but DOS wants things as simple as they can be. ;-) The files edlin.en and msgs-en.h in the distro are the English-language versions of the catalog and msgs.h, respectively. If I submitted a set of files for every language and compiler in existence, the politics of multiplication would come in, and I would be old and grey (or possibly dead from old age) before that project would be completed. Gregory > On 02/04/2024 1:32 PM EST Eric Auer <e.a...@jpberlin.de> wrote: > > > > I made recompiling Edlin easy for non-programmers, > > so that shouldn't be a problem. You don't have to > > know a lick of C to recompile it. > > One would still need the toolchain, so it would > be great if there could be somebody who already > has it (and does know C, just in case) who would > volunteer as the "send me your NLS updates for > EDLIN and I will make sure an updated EDLIN zip > will get published" person. Or, as said, a CI way. > > Eric > > PS: As mentioned on BTTR in the Book8088 compat thread > (which found out that SYS CONFIG GLOBALENABLELBASUPPORT=0 > can work around some crash in XT-IDE BIOS!) even seemingly > easy to use compiles fail in *unexpected* ways, e.g. OW > 2.0 compiles kernels in Linux, but only 1.9 does in DOS? _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
