tinycc-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] Understanding tcc Makefile


From: grischka
Subject: Re: [Tinycc-devel] Understanding tcc Makefile
Date: Sun, 06 Dec 2009 20:02:44 +0100
User-agent: Thunderbird 2.0.0.23 (Windows/20090812)

k1w1 wrote:
Hi,

I am trying to understand the Makefile. It seems to me that bcheck.o needs to be built with tcc since it will be linked with the rest of the user code built with tcc. However I can't see in the makefile how this happens. In fact on my machine it is built with gcc when I run make. This seems wrong.

Anyone got any ideas about what I am missing?

On windows, all objects that tcc wants to use must be compiled
with tcc itself.  In particular not with mingw-gcc.

BTW, I have my refactored code working under Windows (Borland C++Builder) and cygwin.

Well, basically you did some nice things and I'm sure we want some
of that, however there might be some problems with your new file
structure.  It's not that I personally don't like it, is is just
that it is not strictly necessary.

So now that you ripped everything into pieces and by the way have
learned how tcc works, could I maybe convince you to join the files
back _somehow_ as they were before?

Of course it is your branch and you can do with it what you want,
but then again cooperation such as merging each other's new features
is much easier if branches are not completely different.

Say, I could maybe agree to one more C file, such as tccrun.c (for
the -run support stuff), and maybe one additional .h file for each
processor target, such as i386-gen.h, arm-gen.h, etc.

What do you think?

Now I am trying to get the bounds checking code
to work on the same environments.

Note that we do not support bounds checking on windows currently.
I don't say it is not possible but it will not work out of the
box.

--- grischka





reply via email to

[Prev in Thread] Current Thread [Next in Thread]