Re: [Tinycc-devel] autoconfiscation

[Gregg Reynolds]

On 8/28/07, Rob Landley <address@hidden> wrote:
...
> Building the entire project, including all cross compiler targets, the build
> currently does this:
>
> cc -O2 -g -Wall -fsigned-char -Os -mpreferred-stack-boundary=2 -m386 \
>         -malign-functions=0 -o tcc tcc.c -lm -ldl
> cc -O2 -g -Wall -fsigned-char -Os -mpreferred-stack-boundary=2 -m386 \
>         -malign-functions=0 -DTCC_TARGET_ARM -DTCC_ARM_EABI \
>         -o arm-tcc tcc.c -lm -ldl
> cc -O2 -g -Wall -fsigned-char -Os -mpreferred-stack-boundary=2 -m386 \
>         -malign-functions=0 -DTCC_TARGET_C67 -o c67-tcc tcc.c -lm -ldl
> cc -O2 -g -Wall -fsigned-char -Os -mpreferred-stack-boundary=2 -m386 \
>         -malign-functions=0 -DTCC_TARGET_PE -o i386-win32-tcc tcc.c -lm -ldl
> cc -O2 -Wall -c -o libtcc1.o libtcc1.c
> cc -c -o i386/alloca86.o i386/alloca86.S
> cc -c -o i386/bound-alloca86.o i386/bound-alloca86.S
> ar rcs libtcc1.a libtcc1.o i386/alloca86.o i386/bound-alloca86.o
> cc -O2 -Wall -c -o bcheck.o bcheck.c
> cc -O2 -g -Wall -fsigned-char -Os -mpreferred-stack-boundary=2 -m386 \
>         -malign-functions=0 -DLIBTCC -c -o libtcc.o tcc.c
> ar rcs libtcc.a libtcc.o
>
> The above can actually be _simplified_ somewhat, I suspect.  Why, exactly,
> does this need more complexity than a very small shell script?

I just came across http://kegel.com/crosstool/ and took a (very) quick
look at the code.  It builds gcc/glibc across a gazillion platforms,
but it looks like it does it all with bunch of small shell scripts.
Which is essentially what we'd want for tcc, only on a smaller and
less hairy scale, and with a simple configure/makefile instead of the
Autotools build system gcc uses.  I think it's worth looking at as a
model for a tcc system, especially since a c compiler wants a c
standard lib.  It would be nice to be able to tell the build system
something like "Go forth, and build ye me a tcc compiler with a uClibc
library!".

-gregg