Re: [Freedos-devel] FreeDOS Branded C/C++ Toolchain

Hi, I did a build of OW 2.0 (it was rebranded) but nothing else was changed at this point. It turns out the best way to build it was on Windows. I tried Linux and failed and the path was too deep for MS-DOS to be used for building. > On Jan 18, 2018, at 1:18 AM, Rugxulo

Re: [Freedos-devel] FreeDOS Branded C/C++ Toolchain

Hi, On Wed, Jan 17, 2018 at 11:11 PM, Antony Gordon wrote: > > AFAIK no one on this project is interested in building a C compiler from > scratch for > the purposes of developing FreeDOS. Nobody's directly working on such, AFAIK, unless you count SmallerC (which is not DOS

Re: [Freedos-devel] FreeDOS Branded C/C++ Toolchain

Hi, AFAIK no one on this project is interested in building a C compiler from scratch for the purposes of developing FreeDOS. DJGPP can’t reliably generate code for all the DOS modes which rules it out, MSC and the Borland compilers. Pacific C is free but we only have access to the binary

Re: [Freedos-devel] FreeDOS Branded C/C++ Toolchain

> The OpenWatcom toolchain is the reference compiler for > FreeDOS. when I started with FreeDOS, MSC 6.x was the recommended compiler to use for FreeDOS. later this became TurboC (because it was free), then Watcom C (because it's free and open), and in not so far future people will be asking for

Re: [Freedos-devel] FreeDOS Branded C/C++ Toolchain

. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Remitente:Antony Gordon <cuzint...@gmail.com> Destinatario: Technical discussion and questions for FreeDOS developers. <freedos-devel@lists.sourceforge.net> Fecha:lunes, 15 de enero de 2018, 5:47:52 Asunto: [Freedos-devel] FreeDOS Branded C/C++ Toolch

Re: [Freedos-devel] FreeDOS Branded C/C++ Toolchain

Hi, I’m going to address all the emails at once instead of replying to multiple emails so it will be pretty easy to follow (I think). Jerome, it initially looks like that because I haven’t had the time to devote to fully building this idea out. Also, due to the amount of things involved in

Re: [Freedos-devel] FreeDOS Branded C/C++ Toolchain

On Sun, 14 Jan 2018, Jim Hall wrote: Hi Tony I appreciate the effort, but I'm not sure I like the optics of re-branding another project's work as "FreeDOS." That will seem like we're trying to grab someone else's stuff and claim it as our own - which we're not. QFT. Personal opinion: A

Re: [Freedos-devel] FreeDOS Branded C/C++ Toolchain

Hi Tony I appreciate the effort, but I'm not sure I like the optics of re-branding another project's work as "FreeDOS." That will seem like we're trying to grab someone else's stuff and claim it as our own - which we're not. We've rarely branded anything "FreeDOS" except for a few core things.

Re: [Freedos-devel] FreeDOS Branded C/C++ Toolchain

Hello, Not sure I like renaming someone else’s tools and slapping the FreeDOS name on them. You really need to ask Jim Hall if he is fine with you using the FreeDOS name this way. Putting that issue aside for the moment, what is the advantage of this toolchain? You said you spent over a

Re: [Freedos-devel] FreeDOS Branded C/C++ Toolchain

Hi all and Happy New Year, I sent a screen shot, not knowing that there was a size limit on the emails, so I’m resending as a text only message. I have been working on a project for FreeDOS for well over year and I think it’s about ready for prime time. I thought it would be cool if there was