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. And that's always been done by the person who wrote the program; not by us. I don't see the need to rename OpenWatcom C/C++ to FreeDOS C/C++, or OpenWatcom Assembler to FreeDOS Assembler. If there's something new you've added to OpenWatcom in the process of this work, I think it's better to contirbute those changes back to the OpenWatcom folks. Jim On Sun, Jan 14, 2018 at 11:12 AM, Antony Gordon <cuzint...@gmail.com> wrote: > 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 a > FreeDOS branded toolchain, so I worked on the OpenWatcom code and re-branded > it to FreeDOS. It still has all of the OpenWatcom copyright information, > here’s an example from the WASM assembler. > > [Output from WASM] > FreeDOS Assembler Version 2.0 beta Jan 13 2018 21:40:47 (32-bit) > Copyright (c) 2002-2017 The Open Watcom Contributors. All Rights Reserved. > Portions Copyright (c) 1992-2002 Sybase, Inc. All Rights Reserved. > Source code is available under the Sybase Open Watcom Public License. > See http://www.openwatcom.org/ for details. > > [Output from WCL] > FreeDOS C/C++ x86 16-bit Compile and Link Utility > Version 2.0 beta Jan 13 2018 22:29:44 (16-bit) > Copyright (c) 2002-2017 The Open Watcom Contributors. All Rights Reserved. > Portions Copyright (c) 1988-2002 Sybase, Inc. All Rights Reserved. > Source code is available under the Sybase Open Watcom Public License. > See http://www.openwatcom.org/ for details. > > The cool thing is that both the Watcom and FreeDOS toolchain can co-exist (as > long as you set your paths properly. I am going to install it in FreeDOS and > look for some code to compile in FreeDOS to see if it will work, especially > since this is 2.0 and not the 1.x branch. > > If anyone else would like to take it for a spin, let me know. > > -Tony > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
