>> But it's clear now, that GCC/DJGPP is not a good choice=20=
to=20
do
>> this.
>Why? Too big?
too big, too many files, too complicated the installation,
too diffi=
cult=20
to explain to someone who is not a programmer.
>> So, is there another compiler which someone can recommen=
d=20
for this
>> purpose ?
>
>Okay, I'll l=
ist=20
the reduced files for OpenWATCOM. I'm not sure if
>it is=20
really any smaller...
>
>> (easy to install, hand=
les=20
basic C-commands, few and short=20
files,
>>compatible,
>> free from=20
copyright/license etc.)
>
>I have yet to see a Publi=
c=20
Domain C compiler. Everything has some
>type of=20
restriction... And, if it doesn't, it is usually=20
too
>incomplete to be useful.
C is the most standard language, I think. Used for most=20
University
research. Lots of software has been written in C. So we should=
=20
have
this compiler already. It should even be included in the OS.
If i=
t=20
isn't there, then something must be wrong with the
whole computer busynes=
s.=20
(IMO)
>> I would even accept if only a subset of C-commands is=20
compiled
>> and speed is not so=20
important.
>
>You can also use CIL (C Intermediate=20
Language) (link below) to
>simplify C code as much as you=20
want. CIL is a C to C "translator"
>used to eliminate codi=
ng=20
errors but also reduces complexity and
>posix code to simpler=20
code.
>
>>But it should have good=20
compatibility
>> with GCC/DJGPP.
>
>N=
ot=20
likely, due to POSIX, unless you switch to Linux. There=20
are
>alot of simple C compilers for Linux e.g., TCC by F. Bellar=
d=20
(links
>below).
I don't know about Linux. Maybe it was a mistake not to choose Linuxin=20
the first place, but now I'm too lazy to change.
>Sincerely,
>
>Rod=20
Pemberton
>
>
>To use the reduced file s=
ets=20
for WATCOM, you'll need to put these
>in a .bat file and run=20
it:
>SET WATCOM=3DC:\WATCOM
>SET=20
EDPATH=3DC:\WATCOM\EDDAT
>SET=20
INCLUDE=3DC:\WATCOM\H;C:\WATCOM\H\NT
>
>A minimal se=
t of=20
files for DOS RM=20
OpenWATCOM:
>C:\watcom\binw\wcc.exe
>C:\watcom\binw\=
wcl.exe
>C:\watcom\binw\wlink.exe
>C:\watcom\binw\wl=
ink.lnk
>C:\watcom\binw\wlsystem.lnk
>C:\watcom\binw=
\wstub.exe
>C:\watcom\h\*.h
>C:\watcom\h\sys\*.h
=
>C:\watcom\lib286\dos\clibs.lib
>C:\watcom\lib286\dos\e=
mu87.lib
>C:\watcom\lib286\dos\graph.lib
>C:\watcom\=
lib286\math87s.lib
>
>A=20
minimal set of files for DOS PM=20
OpenWATCOM:
>C:\watcom\binw\wcc386.exe
>C:\watcom\bi=
nw\wcl386.exe
>C:\watcom\binw\wlink.exe
>C:\watcom\b=
inw\wlink.lnk
>C:\watcom\binw\wlsystem.lnk
>C:\watco=
m\binw\wstub.exe
>C:\watcom\h\*.h
>C:\watcom\h\sys\*=
.h
>C:\watcom\lib386\dos\clib3r.lib
>C:\watcom\lib38=
6\dos\clib3s.lib
>C:\watcom\lib386\dos\emu387.lib
>C=
:\watcom\lib386\dos\graph.lib
>C:\watcom\lib386\math387r.lib
=
>C:\watcom\lib386\math387s.lib
>C:\watcom\lib386\math3r=
.lib
>C:\watcom\lib386\math3s.lib
why don't they put these into one file ?
>Simple C compilers for DOS:
>
>smallC=
86=20
and smc88dos from=20
here:
>http://www.retroarchive.org/cpm/archive/unofficial/downlo=
ad/
link doesn't work
>smc386c will could easily be retargetd to tasm,=20
etc...
>http://www.physics.rutgers.edu/~vitchev/smallc-i386.html=
smc386c.c doesn't compile with gcc3.2
>CIL (C Intermediate Language)
>CIL (C Intermediat=
e=20
Language)
http://manju.cs.berkeley.edu/cil/=
no compiler. And tons of documentation to read
>There is some limited 16bit support for=20
DJGPP
>
>DJGPP's gcc patches/djlink/nasm
link doesn't work
>http://www.delorie.com/djgpp/16bit/djlink/
I don't understand this. What is it ? And it seems that you need
a=20
compiler anyway.
>http://www.delorie.com/djgpp/16bit/
"This is not for the average programmer. This stuff does not=20
install
easily and doesn't work well yet! Don't use unless you are=
=20
prepared
to fix any bugs you find yourself."
>Simple C compilers floating around the internet that should=20
compile
>for Linux:
no Linux
>Small C by Ron Cain (large number of=20
microprocessors)
>FBCC and TCC by Fabrice Bellard
>B=
CC=20
by Bruce Evans (from ELKS)
>Linux's Dev86 (from=20
ELKS)
>OXCC C Compiler by Norman Culver
>PCC by C Wa=
re=20
Corporation
>Pacific C by Hitech Soft
>Amsterdam=20
Compiler Kit
>Micro C by Dave Dunfield
>OSD (include=
s C=20
compiler) by Chris Giese
Wouldn't it be nice if programmers could attach their source=20
and
their compiler to the executables and people could easily edit
the=
=20
executable - even non-programmers (e.g. output commands or
other simple=20
things).
And then the changed executable could be run to recompile itself=
=20
?
Imagine this newsgroup-dialogue :
Q:
>can I change=20=
the=20
size of the monster in the upper right corner
> in level 7 of ga=
me=20
xyz ?
A:
> load xyz.exe into your editor and replace the 5 in=
=20
line 745 by an 8
> and then recompile by running "xyz=20
-compile". xyz.exe will change itself
> with the new monst=
er=20
included. You can recover the old version,
> "xyz -old"
-Guenter.