I am sure Jiri will be interested in those DOS library enhancements:
https://github.com/open-watcom/open-watcom-v2
As for the fork, I see an additional problem, that will be outdated since it
will not contain latest fixed by Jiri.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
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++ Toolchain
Archivos: <none>
--====----====----====----====----====----====----====----====----====----===--
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
simply building OpenWatcom, i wanted to make sure it would compile and work
before I did anything else major.
Jim and Steve, some of the reasons I am wanted to build a custom compiler
toolchain based on OpenWatcom (kind of like what Microsoft did with Lattice C
in 1983) is
The OpenWatcom toolchain is the reference compiler for FreeDOS.
Since the source is freely available with a license as such (instead of some of
the abandoned but freely available compilers) it can be specifically customized
for FreeDOS
Once completely built, all of the custom libraries that have been developed (or
modified) for use with FreeDOS can be included with it, thereby making a
customized toolchain.
In the customized toolchain, all the non FreeDOS/DOS related stuff (Linux,
Win32, Win64, and OS/2) would be removed. The OpenWatcom project MAY be
interested in the custom libraries that we include specifically for FreeDOS
development, and if so, I’d gladly send them over for inclusion, but I think
the design goals of the OW project are different (at least for the C portion)
which is making it compliant with the newer C/C++ standards and perhaps the
Win32 and Win64 stuff.
FreeDOS doesn’t have to be in the name, but I think having it there will
signify while this is OpenWatcom, it will be a customized version tailored
specifically for FreeDOS.
-Tony
On Jan 14, 2018, at 6:21 PM, Steve Nickolas <usots...@buric.co> wrote:
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 "FreeDOS C" toolchain should really, IMO, if it should even
exist, be a scratch one, not a rebadging of another toolchain.
-uso.
------------------------------------------------------------------------------
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
