As I wrote in my reply to Jim's email, I don't think introducing additional toolchains makes any sense. In fact it would be a good idea to have all 'official' packages that are based on C compile with OWC. I don't know if that has changed, but I remember MKEYB at some point required Turbo-C to compile. DOS isn't usually run in huge-arse environments with terra bytes of HDD space, so it might be a good idea to limit the number of toolchains we need to build packages. If nothing else, it also reduces the number of testing required.
On Sat, 14 Dec 2024 at 15:34, Jerome Shidel via Freedos-devel <freedos-devel@lists.sourceforge.net> wrote: > > Hi, > > On Dec 14, 2024, at 9:13 AM, Bruce Axtens via Freedos-devel > <freedos-devel@lists.sourceforge.net> wrote: > > > This IA-16 GCC? > https://sourceforge.net/p/freedos/news/2022/01/ia-16-gcc-toolchain-and-libi86-library-jan-2022-version > > -Bruce > > > The one you want used to be on GitHub [1], > However, the developer moved most of the IA16 stuff to GitLab [2]. > There is also some IA16 dev tools on the FreeDOS Interim Test Build BonusCD > [3]. However, it was only recently discovered that TKChia moved most of those > to GitLab. Therefore, those packages have not been updated. > > [1] https://github.com/tkchia/ > [2] https://gitlab.com/tkchia/ > [3] > https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ > > _______________________________________________ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel > > _______________________________________________ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
