From: "Fabrice Bellard":
> grischka wrote:
> > Future plans? Well, what about splitting the sources into parts
> > and making them compile from distinct object files, now? WDYT?
>
> OK provided there are not many more .c and .h files as there are now.
Here is a suggestion:
- tcc.h ~1000
On Thu, Apr 3, 2008 at 1:50 AM, grischka wrote:
> Latest new features are compilation from standard input and
> multiple verbosity levels (tcc -v, -vv, -vvv).
>
> Get it from here:
> http://fabrice.bellard.free.fr/tcc/
>
> Or here:
> http://savannah.nongnu.org/projects/tinycc
>
> Future plans? Wel
grischka wrote:
> Latest new features are compilation from standard input and
> multiple verbosity levels (tcc -v, -vv, -vvv).
>
> Get it from here:
> http://fabrice.bellard.free.fr/tcc/
>
> Or here:
> http://savannah.nongnu.org/projects/tinycc
>
> Future plans? Well, what about splitting the s
On Wed, Apr 02, 2008 at 07:50:36PM +0200, grischka wrote:
>Future plans? Well, what about splitting the sources into parts
>and making them compile from distinct object files, now? WDYT?
Sounds like a good thing to me (not a volunteer, atm).
I would start with splitting the LIB into a separate s
Latest new features are compilation from standard input and
multiple verbosity levels (tcc -v, -vv, -vvv).
Get it from here:
http://fabrice.bellard.free.fr/tcc/
Or here:
http://savannah.nongnu.org/projects/tinycc
Future plans? Well, what about splitting the sources into parts
and making them c
