> On 6/2/2025 16:29, Jim Hall via Freedos-devel wrote: [..] > > email) but source code is not provided. Micro-C provides the source > > code, but the COPY.TXT is not an open source license like MIT or GNU > > GPL or something like that. It literally says: [..]
On Thu, Feb 6, 2025 at 1:48 PM Bruno Ribeiro via Freedos-devel <freedos-devel@lists.sourceforge.net> wrote: > > I'm not a lawyer but it seems to me this adhoc "license" is overall in > the spirit of FLOSS (nevermind its vagueness and potential loopholes). > Would Micro-C be considered for inclusion in FreeDOS? It's a pretty good C compiler, and once upon a time I remember that we did include some Micro-C things in FreeDOS, and maybe even Micro-C itself (this would have been a while back, I don't remember the details very clearly anymore). But in more recent distributions, we've had to balance what we include on the CDs. We can't open up the floodgates to include every niche compiler just because one person thinks it's cool. And compilers are kind of big anyway, you can't include very many before the CD gets full. We already include OpenWatcom C, ia-16 GCC, and BCC. Plus FPB (Pascal) and FBC and BWBasic (BASIC) plus other compilers, assemblers (NASM, JWASM, FASM, ..) and development tools & libraries. So that's a long answer to say: probably not going to include Micro-C anytime soon. _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
